On Mon, Apr 14, 2014 at 06:39:43PM +0200, Helmut Grohne wrote: > When cross building a gcc stage3 with_deps_on_target_arch_pkgs=yes, I > noticed that libgccX is uninstallable, because it's dependency on > gcc-4.8-base is not fulfilled (the native one rightfully isn't > M-A:foreign). I believe that gcc should be building that package and am > thus attaching a patch to fix that.
Elaborating: The situation this patch addresses a forward cross build of gcc that sets with_deps_on_target_arch_pkgs=yes. In this case gcc emits (among others) a libgcc1:arm64 package. (Taking DEB_TARGET_ARCH=arm64 as an example, but it works the same for other architectures.) This libgcc1:arm64 package has a Depends line mentioning gcc-4.8-base. However gcc-4.8-base:arm64 is not among the packages that were built. Thus installation of libgcc1:arm64 fails with a dependency error. The gcc-4.8-base:amd64 package cannot be used to satisfy this dependency, because it is marked M-A:same. The proposed fix is to cause with_deps_on_target_arch_pkgs=yes to build gcc-4.8-base:arm64, such that both can be properly installed. If this is not the desired fix, then maybe libgcc1:arm64 should drop its dependency on the non-existent gcc-4.8-base:arm64 package? Do you need a build log exposing this issue? I can temporarily drop the patch from rebootstrap. Note that the patch applies to gcc-4.9 as well solving the very same issue there. Hope this helps Helmut -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140508045600.ga14...@alf.mars
