This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Documenting the (dynamic) linking rules for symbol versioning
- From: "Michael Kerrisk (man-pages)" <mtk dot manpages at gmail dot com>
- To: Carlos O'Donell <carlos at redhat dot com>, "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Cc: mtk dot manpages at gmail dot com, linux-man <linux-man at vger dot kernel dot org>, Siddhesh Poyarekar <siddhesh at sourceware dot org>, Rich Felker <dalias at aerifal dot cx>, "H.J. Lu" <hjl dot tools at gmail dot com>
- Date: Sat, 13 May 2017 14:10:28 +0200
- Subject: Re: Documenting the (dynamic) linking rules for symbol versioning
- Authentication-results: sourceware.org; auth=none
- References: <b3a962de-6703-d8b9-18f7-138185171475@gmail.com> <66c61101-f44f-2bbb-5ed2-b43c5d764e76@redhat.com>
Hi Carlos,
On 05/05/2017 09:51 PM, Carlos O'Donell wrote:
> On 04/19/2017 11:07 AM, Michael Kerrisk (man-pages) wrote:
>> The documentation around symbol versioning as used by the glibc dynamic
>> linker (DL) is currently rather weak, and I'd like to add some pieces to
>> various man pages (ld.so(8), dlsym(3), and possibly others) to improve
>> this situation. Before that though, I'd rather like to check my
>> understanding of the rules.
>
> This is great!
>
> Can I make one simple request?
>
> Please post all of your test case and we help you get them checked into
> glibc's regression testsuite so we don't change any of the behaviour you
> have documented without noticing it.
>
> I'd like us to agree to ensure we cover everything you mention in a
> regression test.
I'm happy to help here, bug do not have a CLA, and do not plan
to get one. But, I can place whatever code might be useful under
a permissive license (assuming that works for you).
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/