Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Jun 2009 18:36:11 -0700
From:      Sam Leffler <sam@freebsd.org>
To:        Chuck Robey <chuckr@telenix.org>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: ARMv7 - EABI - Cross Compiler
Message-ID:  <4A27250B.2000100@freebsd.org>
In-Reply-To: <4A26FB34.7000209@telenix.org>
References:  <77926.36276.qm@web59405.mail.ac4.yahoo.com>	<4A2555C8.8040405@freebsd.org> <4A26FB34.7000209@telenix.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey wrote:
> Sam Leffler wrote:
>   
>> Vassilis Laganakos wrote:
>>     
>>> Hello,
>>>
>>> I recently started working on getting a later version of GCC as a
>>> cross-compiler for FreeBSD.
>>> The main reason is that I'm interested in having support for the "new"
>>> ARM EABI that will give the benefits of ARMv5TE onwards, to all the
>>> boards that use it (Mistral EVM, BeagleBoard, etc)
>>>
>>> I've built gcc 4.4.1 (rev 147925) and binutils (2.19.51.20090527),
>>> using the 7-STABLE headers where appropriate. I'm now trying to built
>>> libc from the same branch. I'm trying to pull out libc from the
>>> building tree, and
>>> build it with the above toolchain so that it will be available to use
>>> it with that (once done, I'll commit a port for this); at the same
>>> time I'm try to drop the GCC 4.4.1 in the build tree to be able to use
>>> it for building the world.
>>>
>>> Please let me know whether I'm  going down the wrong path or not :o)
>>> Tips and advice pointers towards
>>> the right direction would be more than helpful!
>>>
>>> I don't know if someone else is working on something similar, but if
>>> the answer is "yes" I would be quite happy to be of help. If not, any
>>> kind of help would be most appreciated :o)
>>>
>>>   
>>>       
>> Your basic approach sounds fine.  I believe you will find many small
>> changes to base code required by the later version of gcc (depending on
>> compile options).  If you work with HEAD instead of RELENG_7 then these
>> changes can likely be merged and will simplify your effort in the
>> future.  Ideally you should be able to install the gcc port, pull
>> freebsd code, and then use the xdev  build mechanism to cross-build w/
>> the toolchain.
>>     
>
> Doesn't xdev build the 4.2.1 version of gcc, like what's in the tree now?
> That's unacceptable to me, gcc didn't bring in support for the Cortex-A8
> processor until 4.3.0.  I was able to build a cross-gcc easily using a target of
> "arm-linux-gnueabi", but I'm not sure if that sort of gcc will do for building
> FreeBSD.  I'll worry about getting that gcc into the build, but will it work for
> me on a binary basis?
>   

Yes, I was thinking Warner had committed some other stuff he and I had 
talked about.  I haven't touched the buildtools in a while so not sure 
what's required specifically for freebsd (like printf extensions).

    Sam




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A27250B.2000100>