From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] barking up a different tree
Date: Sat, 23 Apr 2011 22:38:52 +0200 [thread overview]
Message-ID: <8762q4aejn.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <BANLkTi=EYF+b=d-LdM=bPXzaZ-7oZh-87A@mail.gmail.com> (Charles Krinke's message of "Sat, 23 Apr 2011 13:01:36 -0700")
>>>>> "Charles" == Charles Krinke <charles.krinke@gmail.com> writes:
Charles> Maybe I am barking up the wrong tree.
Charles> Being able to do "make clean" and *not* have to re-compile the
Charles> uclibc toolchain would get buildroot to an acceptable point
Charles> for the uclibc part of my project.
Just build it once somewhere (E.G. set BR2_HOST_DIR to /opt/toolchain or
whatever), and then just configure BR to use it as an external
toolchain.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-04-23 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 20:01 [Buildroot] barking up a different tree Charles Krinke
2011-04-23 20:38 ` Peter Korsgaard [this message]
2011-04-23 20:46 ` William Wagner
2011-04-23 21:02 ` Charles Krinke
2011-04-25 15:19 ` ANDY KENNEDY
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=8762q4aejn.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