Ross, Actually, no. Other arches can be effected. Currently work on glibc 2.2.x in debian has been depreciated in favor of work on glibc 2.3. In glibc 2.3, i386, ppc and ia64 currently clearly have the libgcc-compat issue addressed. Other arches really should be throughly tested. I have created and posted a perl script which debian developers can use to check their arch for such symbols.
http://lists.debian.org/debian-glibc/2002/debian-glibc-200209/msg00148.html http://lists.debian.org/debian-glibc/2002/debian-glibc-200209/msg00164.html These scripts both first collect a list of symbols from libgcc_s.so.1 and then search binaries/libraries for undefined instances of these symbols. The script then creates a final.list of all the libgcc symbols that need to be on a sysdeps/<arch>/libgcc-compat.c for a given arch and a found.list with a listing of which symbol was found in which file. The first version of the script operates on a listed set of directories and the section version is used to look at the files in archived debs via dpkg-deb. Jack -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
