libc dependency issue,

[yli147]

Hi,

There should no changes in my build system these days, but it comes out with a libc dependency issue, the logs are as below, it is very strange, any clue about it ? Thanks for your feedback !

Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing python function do_rootfs_install
| DEBUG: Executing shell function root_cleandirs
| DEBUG: Shell function root_cleandirs finished
| DEBUG: Executing shell function rootfs_prepare
| DEBUG: Shell function rootfs_prepare finished
| DEBUG: Executing shell function rootfs_configure_isar_apt
| DEBUG: Shell function rootfs_configure_isar_apt finished
| DEBUG: Executing shell function rootfs_configure_apt
| DEBUG: Shell function rootfs_configure_apt finished
| DEBUG: Executing shell function rootfs_do_mounts
| DEBUG: Shell function rootfs_do_mounts finished
| DEBUG: Executing shell function rootfs_install_pkgs_update
| Get:1 file:/isar-apt isar InRelease
| Ign:1 file:/isar-apt isar InRelease
| Get:2 file:/isar-apt isar Release [4994 B]
| Get:2 file:/isar-apt isar Release [4994 B]
| Get:3 file:/isar-apt isar Release.gpg
| Ign:3 file:/isar-apt isar Release.gpg
| Reading package lists...
| DEBUG: Shell function rootfs_install_pkgs_update finished
| DEBUG: Executing shell function rootfs_install_resolvconf
| DEBUG: Shell function rootfs_install_resolvconf finished
| DEBUG: Executing shell function rootfs_import_package_cache
| DEBUG: Shell function rootfs_import_package_cache finished
| DEBUG: Executing shell function rootfs_install_pkgs_download
| Reading package lists...
| Building dependency tree...
| Starting pkgProblemResolver with broken count: 1
| Starting 2 pkgProblemResolver with broken count: 1
| Investigating (0) libc6:riscv64 < none -> 2.34-6 @un puN Ib >
| Broken libc6:riscv64 Depends on libgcc-s1:riscv64 < none @un pH >
| Considering libgcc-s1:riscv64 5001 as a solution to libc6:riscv64 9999
| Done
| adduser is already the newest version (3.128).
| apt is already the newest version (2.5.2).
| dpkg is already the newest version (1.21.9).
| locales is already the newest version (2.34-6).
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
|
| The following packages have unmet dependencies:
| libc6:riscv64 : Depends: libgcc-s1:riscv64 but it is not installable
| W: Target Sources (main/source/Sources) is configured multiple times in /etc/apt/sources.list.d/bootstrap.list:2 and /etc/apt/sources.list.d/bootstrap.list:5
| E: Unable to correct problems, you have held broken packages.
| WARNING: exit code 100 from a shell command.
| DEBUG: Python function do_rootfs_install finished
| ERROR: ExecutionError('/build/tmp/work/debian-sid-ports-riscv64/buildchroot-host/1.0-r0/temp/run.rootfs_install_pkgs_download.108', 100, None, None)
ERROR: Task (/build/../work/isar/meta/recipes-devtools/buildchroot/buildchroot-host.bb:do_rootfs_install) failed with exit code '1'

[amikan]

Hello @yli147
Cross building of riscv64 is not stable (and do not work currently) because of version mismatch between amd64 and riscv64 packages libgcc-s1 and gcc-12-base.
It happens because sid-ports repo is updated not so good and fast as normal sid do, so sync can be lost.
As a quick fix you can set ISAR_CROSS_COMPILE="0" in your local.conf.

[yli147]

Hi Anton, Thanks for your input. But I need do the cross_compile, can I somehow roll-back to use the older riscv64 libc ? Because last week, I can get all my local build work

[amikan]

I see those packages are already in sync and cross build of riscv64 is working now.
You can use Debian Snapshot if this situation will happen again.

[yli147]

Thanks, I enabled Debian Snapshot yesterday, it works.