From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch avr32-toolchain-fix
Date: Tue, 27 Jul 2010 23:07:06 +0200 [thread overview]
Message-ID: <8739v4d479.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <cover.1280264418.git.thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Tue, 27 Jul 2010 23:02:20 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Thomas> Hello,
Thomas> This is the fix for the AVR32 toolchain build problem, but it makes a
Thomas> change that impacts all other architectures as well. Instead of using
Thomas> an incorrect --prefix=/usr for binutils and gcc, we use the correct
Thomas> --prefix=$(STAGING_DIR)/usr.
Thomas> With this fix in place, I can build the AVR32 toolchain and an AVR32
Thomas> system with Busybox and DirectFB. However, I couldn't test it as I
Thomas> don't have ARV32 hardware and Qemu doesn't support AVR32.
Thomas> I have also tested an ARM internal Buildroot toolchain + DirectFB, it
Thomas> builds and runs in Qemu. I also tested an ARM external Buildroot
Thomas> toolchain + DirectFB system, it builds and runs in Qemu as well.
Pulled and pushed, thanks!
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2010-07-27 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:02 [Buildroot] [pull request] Pull request for branch avr32-toolchain-fix Thomas Petazzoni
2010-07-27 21:02 ` [Buildroot] [PATCH 1/3] binutils,gcc: use correct --prefix Thomas Petazzoni
2010-07-27 21:02 ` [Buildroot] [PATCH 2/3] toolchain: Remove now-unused variables Thomas Petazzoni
2010-07-27 21:02 ` [Buildroot] [PATCH 3/3] toolchain: remove redundant and incorrect --with-build-time-tools option Thomas Petazzoni
2010-07-27 21:07 ` Peter Korsgaard [this message]
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=8739v4d479.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.