Matthias Klose wrote: > libgcc2 and libgcc4 are missing. But I don't like it. Why stop at > libgcc/libgomp, and not at libstdc++ and libgfortran?
Are there symlinks under /usr/lib/gcc hard-coding the path to 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. Good idea. By the way, Andy, could you give a quick reminder of what you are using gcc 4.2 and 4.3 to do? If we are lucky, there's another way to do it; and if not, it would help in providing motivation for keeping them installable, as in Matthias's example below: > 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. Thanks. Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
