Date: Fri, 19 Jan 2001 04:56:32 -0800 From: "David O'Brien" <obrien@NUXI.com> To: Paul Becke <pbecke@javagear.com> Cc: freebsd-arm@FreeBSD.ORG Subject: Re: arm toolchain Message-ID: <20010119045632.A34811@dragon.nuxi.com> In-Reply-To: <3A67BBB1.5B322CAE@javagear.com>; from pbecke@javagear.com on Thu, Jan 18, 2001 at 09:59:45PM -0600 References: <3A64D209.F5397350@javagear.com> <20010118192710.A95607@dragon.nuxi.com> <3A67BBB1.5B322CAE@javagear.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 18, 2001 at 09:59:45PM -0600, Paul Becke wrote: > > > ftp://64.24.60.4/pub/arm-binutils.tar.gz > > > ftp://64.24.60.4/pub/arm-gcc.tar.gz > > > ftp://64.24.60.4/pub/arm-gdb.tar.gz > > > > There is already an ELF arm port in devel/. i will look at yours in a > > few weeks and see if there is anything I should combine with the existing > > one.s > > > > > I would be happy to contribute these ports to the general FreeBSD ports > > > collection. I also suggest removing the older arm-aout-* ports. What > > > is the proceedure for obtaining access to update my own ports on the > > > FreeBSD site? > > > > Why should they be removed??? Maybe someone needs a.out support. > > They can be left, it just seems redundant to have multiple ports, when one > set could handle aout, elf, netbsd or any other format using linker switches. Linker switches will not work for the compiler. :-) Trust me, we do not want to hacke up GCC to be able to handle multiple back ends. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arm" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010119045632.A34811>