On 10 March 2012 10:49, William Mills <wmi...@ti.com> wrote:
> On 03/08/2012 04:07 PM, William Mills wrote:
>>
>> On 03/08/2012 03:51 PM, Michael Hope wrote:
>>>
>>> On Fri, Mar 9, 2012 at 5:51 AM, William Mills<wmi...@ti.com> wrote:
>>>>
>>>> All,
>>>>
>>>> I need to supply a Linaro toolchain "aligned" (same source code)
>>>> bare-metal
>>>> compiler to a group doing benchmarking on A15.
>>>>
>>> Hi William. I recommend using the exact same tools we use for
>>> building the binary toolchains but reconfiguring for a baremetal
>>> build. That way you can get the Cortex-A15 improvements that we've
>>> been doing in a simple to make binary toolchain.
>>>
>>> I wrote some brief instructions on this yesterday at:
>>> https://wiki.linaro.org/WorkingGroups/ToolChain/BinaryBuild
>>>
>>> Also see the building from source section in the README:
>>> https://launchpadlibrarian.net/93804205/README.txt
>>
>>
>> Thanks for the recommendation Michael. I will do it this way.
>>
>
> As a first step I tried to rebuild the same linaro-arm-linux-gnueabi version
> you guys publish following a flow similar to the wiki page you show above.
>  I used the 2012.02 tarballs from the
> https://launchpad.net/linaro-toolchain-binaries for src and crosstool-NG.
>
> I followed the host setup instructions in the README.txt but then followed
> the wiki build instructions using a config of "linaro-arm-linux-gnueabi"
>
> My machine is Ubuntu 10.04 32 bit as suggested in README.txt and /bin/sh is
> bash.
>
> The build errored out in PPL with some errors deep in the c++ STL templates
> of the lsbcc.
>
> I next cleaned and reran you config again but then ran ct-ng menuconfig to
> deselect using the lsbcc compiler and just use the host gcc.  The build
> finished OK this way.
>
> Do you guys still use 10.04 32 bit as the reference OS or have you moved on?

Yip, it's all as documented.  We use a EC2 cloud instance to build.

The problem is we need to patch the LSB headers and tools to wrok
around some issues in the other tools configurery.  The result is
still LSB compatible.  contrib/linaro/build.mk does this automatically
by calling contrib/linaro/lsb/make-lsb.sh and then putting the result
in the path.

Short story: what you did is right.

-- Michael

_______________________________________________
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Reply via email to