From: lemonoje <lemonoje@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Altera SoC Buildroot external toolchain incompatible error
Date: Thu, 11 May 2017 13:19:29 -0700 (PDT) [thread overview]
Message-ID: <1494533969065-164751.post@n4.nabble.com> (raw)
In-Reply-To: <20170511221419.1e5e9baf@free-electrons.com>
Thomas,
Wow - thanks for the quick reply. I am using the make ... ... nconfig menu
utility. Under Target EABI--->, I had no option for EABIhf, but now I just
selected *"Enable VFP extension support"* which then gives me the Target
ABI--->EABIhf. I should have my C library as glibc, correct?
I get a little further...now stalled at:
>>> toolchain-external Installing to staging directory
/usr/bin/install -D -m 0755
/sf/ArriaX/ltsi_4_1_33/buildroot/output/build/toolchain-external/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/.stamp_staging_installed'
failed
I do not have the 'usr' path under ^^^ path/sysroot
--
View this message in context: http://buildroot-busybox.2317881.n4.nabble.com/Altera-SoC-Buildroot-external-toolchain-incompatible-error-tp164744p164751.html
Sent from the Buildroot (busybox) mailing list archive at Nabble.com.
next prev parent reply other threads:[~2017-05-11 20:19 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 [this message]
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
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=1494533969065-164751.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox