From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Few questions external toolchain
Date: Tue, 25 Feb 2014 14:34:12 +0100 [thread overview]
Message-ID: <530C9BD4.2020201@gmail.com> (raw)
In-Reply-To: <CAAXf6LUnOyzHbSaOZtcBak55CQuKr=zSzzgH8zLkaF7zGPdSVw@mail.gmail.com>
Il 25/02/2014 14:10, Thomas De Schampheleire ha scritto:
> The external toolchain wrapper is created automatically by buildroot
> when the toolchain is 'installed'. However, above I see two different
> paths: /home/marco/dev/fsl-linaro-toolchain/bin/ext-toolchain-wrapper
> and ~/dev/buildroot/output/host/usr/bin/ Have you moved the buildroot
> repository to another location? Normally the toolchain wrapper is
> located in <output>/host/usr/bin, just like the symbolic links that
> point to it. Best regards, Thomas
Thomas,
the first path:
/home/marco/dev/fsl-linaro-toolchain/fsl-linaro-toolchain/bin
is where I put my toolchain.
The second one:
home/marco/dev/buildroot/output/host/usr/bin/
is where buildroot wrapped the toolchain, but of course
/home/marco/dev/fsl-linaro-toolchain/bin/ext-toolchain-wrapper does not
exist!
I tried to let buildroot to download the tarball but it's the same.
In the meanwhile I fix this issue I'm compiling using the built-in
codesourcery toolchain.
Best regards
Marco
next prev parent reply other threads:[~2014-02-25 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 18:18 [Buildroot] Few questions external toolchain Marco Trapanese
2014-02-25 10:17 ` Marco Trapanese
2014-02-25 13:10 ` Thomas De Schampheleire
2014-02-25 13:34 ` Marco Trapanese [this message]
2014-02-25 14:11 ` Thomas De Schampheleire
2014-02-26 16:53 ` Marco Trapanese
2014-02-26 19:42 ` Thomas De Schampheleire
2014-02-26 19:53 ` Marco Trapanese
2014-02-26 21:47 ` Arnout Vandecappelle
2014-02-26 22:46 ` Marco Trapanese
2014-03-17 14:59 ` Thomas De Schampheleire
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=530C9BD4.2020201@gmail.com \
--to=marcotrapanese@gmail.com \
--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.