On 07/20/2011 10:17 AM, Jonathan Nieder wrote: > Jonathan Nieder wrote: > >> 2. Would it make sense to introduce a new package libgcc1-multiarch >> and make libgcc1 into a compatibility package that ships a symlink >> >> /lib/libgcc_s.so.1 -> /lib/$arch/libgcc_s.so.1 >> >> for the sake of smooth partial upgrades? > > i.e., something like this? (Plus the analagous change for libgomp.
libgcc2 and libgcc4 are missing. But I don't like it. Why stop at libgcc/libgomp, and not at libstdc++ and libgfortran? For now, I'll add an unconditional break on gcc-4.1 and gcc-4.3 in libgcc1, which should make people aware of the breakage. Maybe it would be better to backport the multiarch patches to gcc-4.3; while removed in unstable now, the GPC frontend was updated to build for 4.3 instead of 4.1, so a multiarch enabled gcc-4.3 in unstable would make sense. Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e269cba.6010...@debian.org
