From: "thorsten.johannvorderbrueggen@t-online.de" <thorsten.johannvorderbrueggen@t-online.de>
To: crossgcc@sourceware.org
Subject: Problem armhf build after huge multilib merge
Date: Thu, 25 Aug 2016 17:27:00 -0000 [thread overview]
Message-ID: <20160825192644.00b64c20b78dfef416d2f033@t-online.de> (raw)
Hi@all,
i have a problem to build sysroot via buildroot based on a crosstool-ng toolchain ...
Short summary:
I build a crosstoolchain for armhf (https://github.com/tjohann/a20_sdk/blob/master/configs/ct-ng_config) ... to be able to crosscompile i build some libs with buildroot and use them as sysroot ... this was working many times .. but after the multilib merge (https://github.com/crosstool-ng/crosstool-ng/commit/8a4870c2f8788c097d71194cb6d334cef1ae31ab) i will get an error using when i want to build the buildroot parts ... So i think it's a crosstool problem an not a buildroot because it worked bevor the multilib merge ...
Any suggestions? ...
/sbin/make -j1 HOSTCC="/sbin/gcc" HOSTCXX="/sbin/g++" silentoldconfig
make[1]: Verzeichnis „/home/tjohann/src/toolchain_a20_sdk/buildroot“ wird betreten
BR2_DEFCONFIG='' KCONFIG_AUTOCONFIG=/home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/buildroot-config/auto.conf KCONFIG_AUTOHEADER=/home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/buildroot-config/autoconf.h KCONFIG_TRISTATE=/home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/buildroot-config/tristate.config BR2_CONFIG=/home/tjohann/src/toolchain_a20_sdk/buildroot/.config BR2_EXTERNAL=support/dummy-external HOST_GCC_VERSION="4 9" SKIP_LEGACY= /home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/buildroot-config/conf --silentoldconfig Config.in
make[1]: Verzeichnis „/home/tjohann/src/toolchain_a20_sdk/buildroot“ wird verlassen
>>> toolchain-external Configuring
/opt/a20_sdk/toolchain/lib/gcc/arm-none-linux-gnueabi/4.9.4/../../../../arm-none-linux-gnueabi/bin/ld: error: /tmp/cc6yQsd4.o uses VFP register arguments, /home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/.br-toolchain-test.tmp does not
/opt/a20_sdk/toolchain/lib/gcc/arm-none-linux-gnueabi/4.9.4/../../../../arm-none-linux-gnueabi/bin/ld: failed to merge target specific data of file /tmp/cc6yQsd4.o
collect2: error: ld returned 1 exit status
Incorrect ABI setting: EABIhf selected, but toolchain is incompatible
make: *** [package/pkg-generic.mk:194: /home/tjohann/src/toolchain_a20_sdk/buildroot/output/build/toolchain-external/.stamp_configured] Fehler 1
Pls ignore the 4.9.4 of compiler ... i work on some upgrades but it's the same with "mainline" ...
Cheers & thx
Thorsten
--
thorsten.johannvorderbrueggen@t-online.de <thorsten.johannvorderbrueggen@t-online.de>
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
reply other threads:[~2016-08-25 17:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160825192644.00b64c20b78dfef416d2f033@t-online.de \
--to=thorsten.johannvorderbrueggen@t-online.de \
--cc=crossgcc@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).