> Bah. Since you're the pretty much the most active glibc-hppa porter, > I'd do pretty much whatever you suggested for that port. That's like > suggesting that because drepper's not a DD we shouldn't follow his > advice. =) And if it weren't for me begging you to make glibc on HPPA > work, I'd be tempted to come over and bring you food/water until you > finished your NM! ;)
I've had similar accusasions here from elmo and neuro :) With the help of pb I'm working on glibc right now, the issue is that turn-around on builds slows things down. Though I also have taken it upon myself to work on the XFree86 loader for HPPA, which means I get a better understand of the 32-bit relocations. > At Debcamp, Guido and I talked about the idea of parsing out the list of > the failures and setting up a known-failures list instead of just doing > perfect/non-perfect. I have that on my TODO list. There's a couple of > other pieces I want to look at first. That does sound like a good idea. There are about 10-12 failures that HPPA tolerates, but the rest are fatal to userspace. If you want to add something like this to the build process I would be happy to contribute the HPPA list, and even some code :) Though I'll have to wait until glibc works again! I'm on the second path to fixing glibc by tracking back the cvs checkouts by date and seeing where I can finally get a building working version. Cheers, Carlos. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]