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: Wed, 6 Dec 2006 02:08:13 +0100 From: Lennert Buytenhek <buytenh@...tstofly.org> To: "Michael K. Edwards" <medwards.linux@...il.com>, Linux Kernel List <linux-kernel@...r.kernel.org>, Sam Ravnborg <sam@...nborg.org>, linux-arm-toolchain@...ts.arm.linux.org.uk, linux-arm-kernel@...ts.arm.linux.org.uk, crossgcc@...rceware.org Subject: Re: More ARM binutils fuckage On Wed, Dec 06, 2006 at 12:22:26AM +0000, Russell King wrote: > Enabling EABI needs a compiler which supports EABI. That's where I > get fuzzy but recent gcc 4 should be suitable. I have had it suggested > to me that EABI support in the toolchain isn't all that stable at the > moment. I use a bog-standard gcc 4.1.0 to cross-compile all my ARM kernels with, which allows me to build both old-ABI and EABI kernels. (These days I build all kernels in EABI mode with old-ABI compat.) I have not run into any code generation issues with this compiler yet. On the ARM I am running an EABI userland with glibc 2.5, and build stuff natively with vanilla binutils 2.17.50.0.5 (2.17.5.0.3 is 'too old', as it doesn't understand the two argument form of the .movsp directive which one of the gcc ICE fix patches emits), and gcc 4.1.1 with some patches from gcc bugzilla to fix an ICE or two. - 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