Hi, I noticed this as well, but on my side this is a sporadic issue.
I did not investigate this further, though.
Felix
The root-cause of this is the manually modeled dependency chain in
sbuild-chroot.inc around libgcc-<...> and libstd++-<...>. The
assumptions made there are not universally valid, especially not when
packages are taken from debian security (which explains the late
breakage). This was introduced by Jan to reduce the sbuild install
times in 2be866677 and d90f75bd00f. Reverting the changes fixes the
build.
Still I don't fully understand why this breaks non-deterministically.
Best regards,
Felix
>
> Zhihang
I did some further investigation, which revealed a couple of things:
- the DPKG_ARCH=all packages are always build in the sbuild-chroot-host
(even on ISAR_CROSS_COMPILE=0). That makes sense, as Debian does it
like that. However, it also means the sbuild-chroot-host must be
installable on ISAR_CROSS_COMPILE=0
- the sbuild-chroot-host unconditionally installs a cross-compiling
environment (crossbuild-essential-<arch>). That is unnecessary on
global ISAR_CROSS_COMPILE=0 but unproblematic
- the optimization 2be866677 and d90f75bd00f is also applied
unconditionally, breaking the build
I will send a patch that fixes this by only installing the cross
dependencies in sbuild-chroot-host on ISAR_CROSS_COMPILE=1.
This should fix all issues related to "libc6-dev : Depends: linux-libc-
dev".
Felix
>
> Still I don't fully understand why this breaks non-deterministically.
>
> Best regards,
> Felix
>
> >
> > Zhihang
>
> --
> You received this message because you are subscribed to the Google Groups "isar-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+...@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/isar-users/6d581c3f0fc04a4a0d28b38cdd48538c1d8775e8.camel%40siemens.com.