From: Tom Kacvinsky <tkacvins@gmail.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: <OS specific> symbols
Date: Sat, 18 Mar 2023 11:46:05 -0400 [thread overview]
Message-ID: <CAG_eJLewPEhNjUvZ8+ONBEC-4wn-um_Fe_OuTiPN-6SMj91Hog@mail.gmail.com> (raw)
In-Reply-To: <87a60ayuns.fsf@igel.home>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
Hi Andreas,
On Sat, Mar 18, 2023 at 10:57 AM Andreas Schwab <schwab@linux-m68k.org>
wrote:
> On Mär 18 2023, Tom Kacvinsky via Binutils wrote:
>
> > 50: 0000000000939cf0 8 OBJECT <OS specific>: 10 DEFAULT 29
> > _ZGVNSt7collateIwE2idE
>
> 10 is STB_GNU_UNIQUE.
>
> > That is definitely a C++ symbol, but libstdc++.so was not linked
> > dynamically. I am wanting to know how one would get an <OS specific>
> > symbol, and if there is a way of working around this at run time. This
> > tool works fine on CenTOS 7 but not on CentOS 5.
>
> Looks like the CentOS 5 toolchain does not know about GNU_UNIQUE
> symbols.
>
It turns out support for STB_GNU_UNIQUE was implemented in glibc 2.11.
CentOS 7 is glibc 2.17 based (which is why the tool worked there) but the
glibc version on CentOS 5 is 2.5. Because of that, I'm out of luck.
Thanks for pointing me in the right direction.
Tom
prev parent reply other threads:[~2023-03-18 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 11:20 Tom Kacvinsky
2023-03-18 14:57 ` Andreas Schwab
2023-03-18 15:46 ` Tom Kacvinsky [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=CAG_eJLewPEhNjUvZ8+ONBEC-4wn-um_Fe_OuTiPN-6SMj91Hog@mail.gmail.com \
--to=tkacvins@gmail.com \
--cc=binutils@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).