This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Linker exposing private symbols
- From: Alan Modra <amodra at gmail dot com>
- To: Jeffrey Walton <noloader at gmail dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Mon, 27 Aug 2018 11:36:13 +0930
- Subject: Re: Linker exposing private symbols
- References: <CAH8yC8m5obs+uMMC0oVy-HMkbpAZz319fpkigxTGsnm=eX0hfA@mail.gmail.com>
On Sun, Aug 26, 2018 at 04:22:46PM -0400, Jeffrey Walton wrote:
> I have two questions. First, why doesn't the toolchain honor the
> visibility request (why do I need --exclude-libs)? I uess another way
> to put it is, how can symbols be re-exported if they are private?
What makes you think the toolchain is misbehaving? Your visibility
command line options affect the code you are compiling, but you of
course are linking against other object files as well. Maybe all the
symbols that seem unexpected to you come from libcryptopp.a or libc?
> Second, why is ALL case sensitive (and without a diagnostic)?
Seems good to me. You asked ld to exclude All.a symbols.
--
Alan Modra
Australia Development Lab, IBM