lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 2 May 2008 09:43:49 -0400 From: Theodore Tso <tytso@....EDU> To: Vegard Nossum <vegard.nossum@...il.com> Cc: Andrew Morton <akpm@...ux-foundation.org>, Tom Rini <trini@...nel.crashing.org>, torvalds@...ux-foundation.org, bunk@...nel.org, venkatesh.pallipadi@...el.com, davem@...emloft.net, mingo@...e.hu, tglx@...utronix.de, hpa@...or.com, linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com Subject: Re: huge gcc 4.1.{0,1} __weak problem On Fri, May 02, 2008 at 09:18:10AM +0200, Vegard Nossum wrote: > though these are largely untested with Linux Kernel. Most of them are > gcc 3.4.5 (this should in theory compile the kernel correctly), though > I found an e-mail from Ingo saying that you need the -tls versions for > stackprotector to work correctly. This might be a good time to ask if > I should be making gcc 4.1.2s instead. I need to recompile in either > case. Out of curiosity, are you using the stock gcc/binutils from the FSF, or one of the distro toolchains? When we were investigating which compiler/toolchain to use for the LSB Sample Implementation, one of the comments that I got from folks like Eric Troan from rPath and others was that out-of-the-box compiler/toolchain had so many bugs, particularly on non-x86 architectures, that they found they were much better off using a distro-patched/bug-fixed compiler/toolchain and treating that as the upstream. There has been some requests to include cross-compilation functionality into the LSB Build Environment, so I'd be interested in seeing how your work has been going, and maybe there's some opportunity to work together. Is there a mailing list you have for this project? - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists