From: Michael J. Hammel <buildroot@graphics-muse.org>
To: buildroot@busybox.net
Subject: [Buildroot] Migrate .05 to .08/.11 fails with glibc based external toolchain
Date: Wed, 26 Jan 2011 14:03:07 -0700 [thread overview]
Message-ID: <1296075787.3969.22.camel@feynman.coloradoengineeringinc.com> (raw)
In-Reply-To: <20110126203547.09906893@surf>
On Wed, 2011-01-26 at 20:35 +0100, Thomas Petazzoni wrote:
> > make[1]: *** No rule to make target `uclibc_target', needed by
> > `gcc_target'. Stop.
> > make[1]: Leaving directory
> > `/home/mjhammel/src/cei/system_build/bld/buildroot-2010.11'
> >
> You have enabled "native toolchain in the target filesystem" in
> Packages -> Development tools. This is not supported currently with
> external toolchains.
Ah. Excellent. That fixes it. Many thanks!
--
Michael J. Hammel <buildroot@graphics-muse.org>
prev parent reply other threads:[~2011-01-26 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 17:40 [Buildroot] Migrate .05 to .08/.11 fails with glibc based external toolchain Michael J. Hammel
2011-01-26 19:35 ` Thomas Petazzoni
2011-01-26 21:03 ` Michael J. Hammel [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=1296075787.3969.22.camel@feynman.coloradoengineeringinc.com \
--to=buildroot@graphics-muse.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