From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] External Toolchain in latest stable buildroot
Date: Mon, 14 Sep 2009 07:57:41 +0200 [thread overview]
Message-ID: <4AADDB55.3050408@atmel.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901CBEE46@mi8nycmail19.Mi8.com>
H Hartley Sweeten skrev:
> On Friday, September 11, 2009 3:50 AM, Teemu Keskinarkaus wrote:
>> Hi,
>>
>> So I was able to get some of the stuff compile and some not. The
>> external toolchain I'm using is Codesourcery's toolchain for arm.
>> Version is(Sourcery G++ Lite 2009q1-203) (gcc version 4.3.3)
>>
>> I'm quite sure that this is not 100% buildroot problem, but I ask
>> anyway.
>>
>> I hit problems when compiling bootstrap for AT91.
>>
>> Get few of these errors:
>>
>> build/at91sam9263ek/main.o:(.ARM.exidx+0x0): undefined reference to
>> `__aeabi_unwind_cpp_pr1'
>> build/at91sam9263ek/at91sam9263ek.o:(.ARM.exidx+0x0): undefined
>> reference to `__aeabi_unwind_cpp_pr0'
>>
>> I did some digging and it seems that the problem might be in the
>> toolchain, but it might also need some work in buildroot side.
>>
>> Has anyone been able to use CodeSourcerys toolchain to compile buildroot
>> for ARM? Or is anyone even using CodeSourcerys toolchain for ARM?
>>
>> Teemu Keskinarkaus
>
> The Sourcery G++ Lite 2009q1-203 toolchain is a multilib sysroot toolchain.
> I had similar problems trying to get it to work for an EP93XX processor.
>
> I think the AT91 processor is an ARM920T so you need to pass -march=armv4t
> to the toolchain to in order for it to compile the code correctly. This
> is the same option I need for the EP93XX.
The AT91SAM9263 is an ARM926EJ-S.
BR
Ulf Samuelsson
>
> I spent the last three weeks trying to get this toolchain to work correctly.
> I finally got "way" over my head and built my own toolchain with crosstool-ng.
> Personally I would prefer to use a prebuilt external toolchain but at least
> everything works now.
>
> Regards,
> Hartley
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2009-09-14 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 6:48 [Buildroot] External Toolchain in latest stable buildroot Teemu Keskinarkaus
2009-09-11 7:14 ` Thomas Petazzoni
2009-09-11 7:27 ` Teemu Keskinarkaus
2009-09-11 10:49 ` Teemu Keskinarkaus
2009-09-11 17:10 ` H Hartley Sweeten
2009-09-11 17:29 ` Thomas Petazzoni
2009-09-11 17:33 ` H Hartley Sweeten
2009-09-14 5:57 ` Ulf Samuelsson [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-11 6:55 Teemu Keskinarkaus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AADDB55.3050408@atmel.com \
--to=ulf.samuelsson@atmel.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox