public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/52104] go1 fails to link on Solaris 8/9 x86 with native TLS
Date: Fri, 03 Feb 2012 10:56:00 -0000 [thread overview]
Message-ID: <bug-52104-4-7JxTB0VcLu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52104-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52104
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-02-03 10:55:07 UTC ---
> --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-02-03 10:48:16 UTC ---
> Are you sure this is using native TLS?
Not anymore ;-( While Solaris 8 and 9 with gas support native TLS, the
test fails. config.log shows
configure:26332: checking whether the target supports thread-local storage
configure:26396: /var/gcc/regression/trunk/8-gcc-gas/build/./gcc/xgcc
-B/var/gcc
/regression/trunk/8-gcc-gas/build/./gcc/ -B/vol/gcc/i386-pc-solaris2.8/bin/
-B/v
ol/gcc/i386-pc-solaris2.8/lib/ -isystem /vol/gcc/i386-pc-solaris2.8/include
-isy
stem /vol/gcc/i386-pc-solaris2.8/sys-include -o conftest -g -O2 conftest.c
>&5
configure:26396: $? = 0
configure:26396: ./conftest
ld.so.1: conftest: fatal: conftest: object requires TLS, but TLS failed to
initi
alize
/vol/gcc/src/hg/trunk/local/libstdc++-v3/configure[20]: 5945 Killed
configure:26396: $? = 137
configure: program exited with status 137
The problem is with the test, though: before Solaris 10, programs using
native TLS need to be linked with -lthread (which happens implicitly
with -pthread) to get the definition of ___tls_get_addr.
Rainer
next prev parent reply other threads:[~2012-02-03 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-03 10:04 [Bug libstdc++/52104] New: " ro at gcc dot gnu.org
2012-02-03 10:05 ` [Bug libstdc++/52104] " ro at gcc dot gnu.org
2012-02-03 10:06 ` ro at gcc dot gnu.org
2012-02-03 10:12 ` redi at gcc dot gnu.org
2012-02-03 10:21 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-02-03 10:48 ` redi at gcc dot gnu.org
2012-02-03 10:56 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2012-02-03 11:09 ` redi at gcc dot gnu.org
2012-02-03 13:09 ` ro at gcc dot gnu.org
2012-02-05 18:40 ` ebotcazou at gcc dot gnu.org
2012-02-05 19:17 ` redi at gcc dot gnu.org
2012-02-05 23:27 ` ebotcazou at gcc dot gnu.org
2012-02-05 23:57 ` redi at gcc dot gnu.org
2012-02-06 21:37 ` redi at gcc dot gnu.org
2012-02-10 15:23 ` ro at CeBiTec dot Uni-Bielefeld.DE
2012-03-09 16:16 ` [Bug libstdc++/52104] go1 fails to run on Solaris 10/11 x86 with with gld ro at gcc dot gnu.org
2012-03-22 8:55 ` rguenth at gcc dot gnu.org
2012-07-02 12:57 ` rguenth at gcc dot gnu.org
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=bug-52104-4-7JxTB0VcLu@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).