On Sat, Oct 19, 2002 at 03:51:44AM +0900, GOTO Masanori wrote: > > In short, I doubt we will get sufficient testing on problematic > > arches unless we take the leap and push into sid. However I would > > make sure that the findsyms perl script I wrote has been run on the > > debian sid package archives for any arches which we have to create a > > libgcc-compat for to make sure our list of libgcc symbols is complete. > > I'm not sure that is the case for mips yet for example. > > > > http://lists.debian.org/debian-glibc/2002/debian-glibc-200209/msg00164.html > > I want to know mips has this problem (buildd tell us the answer, I hope). > If so, I agree we should fix as you said. I'm investigating this. I have a libgcc-comat patch for mips ( http://honk.physik.uni-konstanz.de/linux-mips/glibc/patches/experimental/libgcc-compat-mips.dpatch ) and am currently scanning the unstable distribution. The tests in my small chroot showed that a libgcc-compat for mips might not be necessary, but only the complete scan will show. Regards, -- Guido
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
