From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc compilation issues on AT91SAM9G20
Date: Fri, 27 Feb 2009 11:37:25 +0100 [thread overview]
Message-ID: <878wnsmahm.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20090227190710.83ff1d6d.william@brodie-tyrrell.org> (William Brodie-Tyrrell's message of "Fri\, 27 Feb 2009 19\:07\:10 +0900")
>>>>> "William" == William Brodie-Tyrrell <william@brodie-tyrrell.org> writes:
>> Are you trying an EABI or OABI build? The aapcs-linux stuff is for
>> EABI.
Hi,
William> EABI, though not for any particular reason other than that's
William> what the linux4sam-provided .config does. The gcc configure
William> only works if I leave the BR2_GCC_TARGET_ABI line out of the
William> .config. The cross compiler (when it's working) is called
William> arm-linux-uclibcgnueabi-gcc so perhaps I should put
William> linux-uclibcgnueabi in the BR2_GCC_TARGET_ABI?
OK, the other at91sam* defconfigs in BR all seems to use OABI. I'll
check EABI.
>> Could you post your .config?
William> It's attached. It's entirely possible there's something
William> that the linux4sam patches do that is missing from this
William> fresh build I'm doing, but I don't know nearly enough about
William> buildroot to spot it. I copied in my old/working .config
William> and local/AT91 directory and ran 'make oldconfig' to update
William> the .config.
OK, I'll take a look at it.
William> PS: when one gets a fresh copy of HEAD from SVN, the scripts/wget.sh
William> file is missing.
Ehh, that's because we don't have a wget.sh (and never had) - Where do
you see any references to a wget.sh?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-02-27 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 8:44 [Buildroot] native toolchain compilation problem William Brodie-Tyrrell
2009-02-25 9:28 ` Peter Korsgaard
2009-02-25 10:12 ` William Brodie-Tyrrell
2009-02-25 10:18 ` Peter Korsgaard
2009-02-26 6:15 ` [Buildroot] gcc compilation issues on AT91SAM9G20 William Brodie-Tyrrell
2009-02-27 9:15 ` Peter Korsgaard
2009-02-27 10:07 ` William Brodie-Tyrrell
2009-02-27 10:37 ` Peter Korsgaard [this message]
2009-02-27 10:49 ` William Brodie-Tyrrell
2009-02-27 11:35 ` 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=878wnsmahm.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