From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] GCC-4.3.3 in toolchain fails to compile
Date: Sun, 24 May 2009 21:37:15 +0200 [thread overview]
Message-ID: <87iqjqfg2c.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <56ea0bb80905212032x1e01cdfbt4c427fc85c9b72e3@mail.gmail.com> (Paul Archer's message of "Fri\, 22 May 2009 13\:32\:40 +1000")
>>>>> "Paul" == Paul Archer <ptarcher@gmail.com> writes:
Paul> Hey all,
Paul> I am trying to build buildroot-2009.05-rc2 for the AT91SAM9G20,
Paul> however I keep getting gcc compiler errors no matter which version I
Paul> pick, either gcc-4.2.4, gcc-4.3.2/3 and gcc-4.4.x also fails. Versions
>> =gcc4.3.2 all fail with the build error below.
Paul> It seems __DTOR_LIST__ is not being defined, but I don't really know
Paul> where to configure this to get it to be defined.
You have:
BR2_ARM_EABI=y
BR2_GNU_TARGET_SUFFIX="linux-uclibc"
Which doesn't make sense. The correct target suffix for eabi is
"linux-uclibcgnueabi". With that change the toolchain builds. Notice
that it will later fail in libusb and strace unless you get the
post-rc2 fixes in git, and that there's no at91sam9g20ek support in
u-boot (well, there is now in u-boot git after the 2009.03 release,
but not in any released versions).
How did you get to that config? Is is based on any defconfig in
buildroot?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-05-24 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 3:32 [Buildroot] GCC-4.3.3 in toolchain fails to compile Paul Archer
2009-05-24 19:37 ` Peter Korsgaard [this message]
2009-05-28 6:14 ` Paul Archer
2009-05-28 8:26 ` Peter Korsgaard
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=87iqjqfg2c.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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