From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Missing symbols for supporting glibc-built libstdc++.so.6
Date: Wed, 24 Jul 2013 12:01:11 -0400 [thread overview]
Message-ID: <20130724160111.GV3249@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130724233611.5bac4fe7@sibserver.ru>
On Wed, Jul 24, 2013 at 11:36:11PM +0800, orc wrote:
> I did not send a report about this especially, just my experiments
> showed that. Just because nvidia blob did not require libstdc++.so at
> all. But others did.
> You can start reading somewhere in long 'Hello' thread about 6 Jul 2012.
>
> Tested now:
> - Hello world prog:
> #include <iostream>
>
> int main()
> {
> std::cout << "Hello, world!" << std::endl;
> return 0;
> }
>
> % g++ test.cc -o test-cpp
> % musl-out/lib/libc.so ./test-cpp
> [lots of "Error relocating..." errors]
> % musl-out/lib/libc.so ./test-cpp 2>&1 | fgrep _ZGVNSt7collateIwE2idE #
> picking one
> % nm /usr/lib/libstdc++.so.6 | fgrep _ZGVNSt7collateIwE2idE
> 00000000002e40d8 u _ZGVNSt7collateIwE2idE
> (man nm says that 'u' is "unique global" and gnu extension)
>
> On musl system there is 'V' instead of 'u'.
> Is my example falls under "glibc-built libstdc++.so.6"?
Yes. Thanks for the report. It's fixed in git. Here is the original
thread on "unique global" support in binutils:
http://www.sourceware.org/ml/binutils/2009-06/msg00016.html
With the latest git, the only symbol errors in glibc-built libstdc++
are the ones I described at the beginning of this thread:
Error relocating .../libstdc++.so.6: __towlower_l: symbol not found
Error relocating .../libstdc++.so.6: __nl_langinfo_l: symbol not found
Error relocating .../libstdc++.so.6: __strxfrm_l: symbol not found
Error relocating .../libstdc++.so.6: __towupper_l: symbol not found
Error relocating .../libstdc++.so.6: __uselocale: symbol not found
Error relocating .../libstdc++.so.6: __wcsxfrm_l: symbol not found
Error relocating .../libstdc++.so.6: __strcoll_l: symbol not found
Error relocating .../libstdc++.so.6: __wcscoll_l: symbol not found
Error relocating .../libstdc++.so.6: __duplocale: symbol not found
Error relocating .../libstdc++.so.6: __wcsftime_l: symbol not found
Error relocating .../libstdc++.so.6: __newlocale: symbol not found
Error relocating .../libstdc++.so.6: __strftime_l: symbol not found
Error relocating .../libstdc++.so.6: __freelocale: symbol not found
Error relocating .../libstdc++.so.6: __strtod_l: symbol not found
Error relocating .../libstdc++.so.6: __strtof_l: symbol not found
Error relocating .../libstdc++.so.6: __iswctype_l: symbol not found
Error relocating .../libstdc++.so.6: strtold_l: symbol not found
Error relocating .../libstdc++.so.6: __wctype_l: symbol not found
(Pathnames elided to make this legible in email.)
Rich
prev parent reply other threads:[~2013-07-24 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 7:55 Rich Felker
2013-07-24 14:20 ` orc
2013-07-24 14:47 ` Rich Felker
2013-07-24 15:36 ` orc
2013-07-24 16:01 ` Rich Felker [this message]
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=20130724160111.GV3249@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).