Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox build fails with external toolchain
Date: Thu, 23 Oct 2008 11:50:31 +0200	[thread overview]
Message-ID: <87y70fd4ig.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <c88e466f0810230239m298d6b09v92a11fdb4ce5f077@mail.gmail.com> (Michel Benoit's message of "Thu\, 23 Oct 2008 11\:39\:22 +0200")

>>>>> "Michel" == Michel Benoit <michel.benoit@sepab.se> writes:

 Michel> Hi,
 Michel> I'm trying to use buildroot to build a rootfs with an external
 Michel> toolchain based on uclibc.
 Michel> I'm using buildroot svn revision 23768
 Michel> The toolchain is based on gcc 4.1.2.

The external toolchain stuff is known to be kinda flaky - But maybe
your problem is the ~ - Could you try with an absolute path to the
external toolchain?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2008-10-23  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23  9:39 [Buildroot] Busybox build fails with external toolchain Michel Benoit
2008-10-23  9:50 ` Peter Korsgaard [this message]
2008-10-23  9:54   ` Roberto A. Foglietta
2008-10-23 13:30   ` Bernhard Reutner-Fischer
2008-10-23 14:38     ` 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=87y70fd4ig.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