Hi, I've built glibc-2.2.93 with CVS glibc-package without any problems on Alpha, and it seems to work OK (onlt tested briefly in a chroot.). The only problem is that the CVS dirs needed to be nuked, or they would end up in the .deb.
I've also toyed with the idea of building optimized packages for certain architectures. IMHO, two extra ones would be sensible: * EV56 * different scheduling * byte/word access instructions * EV6 * different scheduling * wh64 instruction, yields large speedups on memcpy etc. (EV5, PCA56 and EV67 are IMHO not worth the trouble) Unfortunately, there doesn't seem to be support for the library loader to recognize the current architecture and extend the search path accordingly. Is there any documentation available for this? In particular, I cannot find where the tests for the actual hardware ought to be located. -- Falk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]