From: Thomas Drueke <tdrueke@gmx.net>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] crossdev problem
Date: Sat, 10 Sep 2011 18:01:10 +0200 [thread overview]
Message-ID: <4E6B89C6.4040505@gmx.net> (raw)
Hi,
recently I tried to use crossdev to build a toolchain for
"armv7a-softfloat-linux-gnueabi".
The build fails for glibc with
* Messages for package
cross-armv7a-softfloat-linux-gnueabi/glibc-2.12.2:
* Could not find a gcc that supports the __thread directive!
* Please update your binutils/gcc and try again.
* ERROR: cross-armv7a-softfloat-linux-gnueabi/glibc-2.12.2 failed
(unpack phase):
* No __thread support in gcc!
What fails is a compilation test executed in
/usr/portage/sys-libs/glibc/files/eblits/src_unpack.eblit - function
"check_nptl_support".
-> /usr/portage/sys-libs/glibc/files/eblits/common.eblit - function
"want__thread"
-> /usr/portage/eclass/toolchain-funcs.eclass - function
"tc-has-tls" -> "tc-getCC"
I haven't found a log showing the outcome of the compilation making the
available information
restricted somehow.
I tried different approaches for crossdev starting with
crossdev -t armv7a-softfloat-linux-gnueabi
then stated the versions of the host system on the command line:
crossdev -t armv7a-softfloat-linux-gnueabi --g 4.4.5 --l 2.12.2 --k
2.6.39 --b 2.21.1
and browsed the web for a couple of suggested combinations. So far none
worked on my machine.
I wonder if ThreadLocalStorage is supported for ArmV7a or maybe I'm
missing an environment variable ?
Regards,
Thomas
next reply other threads:[~2011-09-10 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 16:01 Thomas Drueke [this message]
2011-10-13 23:14 ` [gentoo-embedded] crossdev problem Mike Frysinger
2011-10-15 8:16 ` [Resolved]: " Thomas Drueke
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=4E6B89C6.4040505@gmx.net \
--to=tdrueke@gmx.net \
--cc=gentoo-embedded@lists.gentoo.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