From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Blackfin Buildroot toolchain issue
Date: Sun, 15 Mar 2015 22:17:22 +0100 [thread overview]
Message-ID: <20150315221722.3645eb35@free-electrons.com> (raw)
Hello Gustavo,
I believe you originally added the support to build a Blackfin
toolchain with the Buildroot internal toolchain backend. Today, I've
added an external Blackfin toolchain built by Buildroot in the
autobuilder, and one build failure occurred with this toolchain, on the
Bellagio package:
http://autobuild.buildroot.org/results/05f/05fa9cb522514e9e5b9e81893f145aab00abd803/build-end.log
I reproduced the build issue here, and the config.log contains:
configure:3298: checking whether the C++ compiler works
configure:3320: /home/thomas/projets/buildroot/output/host/usr/bin/bfin-linux-g++ -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_O
FFSET_BITS=64 -Os -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 conftest.cpp >&5
/home/thomas/projets/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/bfin-buildroot-linux-uclibc/4.5.4/../../../../bfin-buildr
oot-linux-uclibc/bin/ld: a.out: hidden symbol `___udivdi3' in /home/thomas/projets/buildroot/output/host/opt/ext-toolchain/bin/../lib
/gcc/bfin-buildroot-linux-uclibc/4.5.4/libgcc.a(_udivdi3.o) is referenced by DSO
/home/thomas/projets/buildroot/output/host/opt/ext-toolchain/bin/../lib/gcc/bfin-buildroot-linux-uclibc/4.5.4/../../../../bfin-buildroot-linux-uclibc/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
If you have an idea on how to fix this, it would be useful.
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2015-03-15 21:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 21:17 Thomas Petazzoni [this message]
2015-03-15 21:18 ` [Buildroot] Blackfin Buildroot toolchain issue Thomas Petazzoni
2015-03-17 14:20 ` Gustavo Zacarias
2015-03-17 14:30 ` Thomas Petazzoni
2015-03-17 15:08 ` Gustavo Zacarias
2015-03-17 15:13 ` Thomas Petazzoni
2015-03-17 17:55 ` Gustavo Zacarias
2015-03-17 21:34 ` Waldemar Brodkorb
2015-03-17 21:55 ` Thomas Petazzoni
2015-03-17 23:00 ` Waldemar Brodkorb
2015-03-17 13:45 ` Gustavo Zacarias
2015-03-17 13:49 ` Thomas Petazzoni
2015-03-17 14:40 ` Gustavo Zacarias
2015-03-17 14:43 ` Thomas Petazzoni
2015-03-17 16:41 ` Gustavo Zacarias
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=20150315221722.3645eb35@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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.