From: lemonoje <lemonoje@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Altera SoC Buildroot external toolchain incompatible error
Date: Fri, 12 May 2017 07:16:00 -0700 (PDT) [thread overview]
Message-ID: <1494598560669-164820.post@n4.nabble.com> (raw)
In-Reply-To: <20170512155205.526ea00c@free-electrons.com>
Okay, all of that is understood - thank you for further clarification.
However, no matter which method I choose (BR download + extract, or point to
my toolchain) - I still get the same error:
*>>> toolchain-external-linaro-arm 2016.11 Installing to staging directory
/usr/bin/install -D -m 0755
/sf/ArriaX/ltsi_4_1_33/buildroot/output/build/toolchain-external-linaro-arm-2016.11/toolchain-wrapper
/sf/ArriaX/ltsi_4_1_33/buildroot/output/host/usr/bin/toolchain-wrapper
ln: failed to create symbolic link
?/sf/ArriaX/ltsi_4_1_33/buildroot/output/host/usr/ARM-buildroot-linux-gnueabihf/sysroot/usr/lib?:
No such file or directory
package/pkg-generic.mk:255: recipe for target
'/sf/ArriaX/ltsi_4_1_33/buildroot/output/build/toolchain-external-linaro-arm-2016.11/.stamp_staging_installed'
failed
make: ***
[/sf/ArriaX/ltsi_4_1_33/buildroot/output/build/toolchain-external-linaro-arm-2016.11/.stamp_staging_installed]
Error 1
make: Leaving directory '/sf/ArriaX/ltsi_4_1_33/buildroot'*
Maybe I should save my config, delete the BR directory, re-clone and
checkout, and try again?
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Altera-SoC-Buildroot-external-toolchain-incompatible-error-tp164744p164820.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2017-05-12 14:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 19:51 [Buildroot] Altera SoC Buildroot external toolchain incompatible error lemonoje
2017-05-11 20:14 ` Thomas Petazzoni
2017-05-11 20:19 ` lemonoje
2017-05-11 20:51 ` Thomas Petazzoni
2017-05-11 20:46 ` lemonoje
2017-05-11 21:23 ` Thomas Petazzoni
2017-05-12 13:11 ` lemonoje
2017-05-12 13:52 ` Thomas Petazzoni
2017-05-12 14:16 ` lemonoje [this message]
2017-05-12 14:45 ` lemonoje
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=1494598560669-164820.post@n4.nabble.com \
--to=lemonoje@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.