Buwalda, A. posted <[EMAIL PROTECTED]>, excerpted below, on Fri, 15 Apr 2005 13:22:07 +0200:
> $ gcc-config -l > [1] x86_64-pc-linux-gnu-3.4.2 > [2] x86_64-pc-linux-gnu-3.4.2-hardened > [3] x86_64-pc-linux-gnu-3.4.2-hardenednossp > [4] x86_64-pc-linux-gnu-3.4.3-20050110 * > [5] x86_64-pc-linux-gnu-3.4.3-20050110-hardened > [6] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednopie > [7] x86_64-pc-linux-gnu-3.4.3-20050110-hardenednossp > > To be honest, I'm not sure which config to switch to, since I'm not > running a hardened system, or is the default hardened since 2005.0? The default is not (yet) hardened, altho I'm sure the hardened devs wouldn't mind if it was, giving them a bit more help with amd64 bugs from the amd64 herd. You probably want the one that's starred, the non-hardened version. Try switching away from it and back to it, just in case something got stuck. (Guuuyyy! I thought I left that sentence back on MSWormOS =8^(, but it certainly can't hurt!) If that doesn't help, thry RR's suggestion -- run fix-libtool_files.sh with the /bad/ version, /not/ the good one, as a parameter. Keep this little tool ready in your gentoo toolbelt, as it comes in handy more frequently that it really should be needed. Consider using it every time you get *.la file errors, as it very often fixes them. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- [email protected] mailing list
