| 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
| ||
|
Message-ID: <20071214104158.6d256b7b@dhcp-252-066.norway.atmel.com> Date: Fri, 14 Dec 2007 10:41:58 +0100 From: Haavard Skinnemoen <hskinnemoen@...el.com> To: Adrian Bunk <bunk@...nel.org> Cc: linux-kernel@...r.kernel.org Subject: Re: Working upstream toolchain for avr32? On Thu, 13 Dec 2007 20:56:17 +0100 Adrian Bunk <bunk@...nel.org> wrote: > AFAIK the latest available AVR32 toolchains are some patched gcc 4.0 and > some patched binutils 2.17, and avr32 is currently the only architecture > in the kernel where upstream of both of them is not capable of building > a kernel for the architecture. gcc 4.2 is available from www.atmel.com. But I agree that it's unfortunate that avr32 support isn't available upstream. > ALthough not technically a requirement, it would be nice if all Linux > kernel archs could be compiled with plain upstream toolchains. We're working on it. I believe the legal issues around copyright assignment, etc. are mostly sorted out now, so I'm hoping we'll start pushing things upstream early next year. > Even more since at some point in the future [1] current toolchains might > no longer be able to compile the then current kernels. I'm not sure if I understood that, but I guess it's always good to have older versions of the toolchain around. Haavard -- 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