This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Add hidden visibility to internal function prototypes
On Mon, 21 Aug 2017, Florian Weimer wrote:
> > The test links with libc.so, but it uses various GMP objects from libc.a.
> >
> > Generically, any test using any objects from libc.a will have problems if
> > those reference hidden symbols (in this case, __assert_fail) from
> > elsewhere in libc.
>
> I don't think linking a test both against libc.a and libc.so is valid.
>
> In other cases, in order to test hidden symbols, we use fully static
> linking instead. Is this something we could do here as well? I don't
> think it would invalidate the tests any more than the current hybrid
> linkage model does.
As far as I know, linking those tests statically would be OK (it would not
significantly affect what they are testing). That's atext-exp,
atest-sincos, atest-exp2 that are using internal GMP objects from libc.a;
I don't know if other tests, in math/ or elsewhere, also link against
particular libc.a objects.
--
Joseph S. Myers
joseph@codesourcery.com