This is the mail archive of the
mailing list for the glibc project.
Re: What does LAV_CURRENT mean backwards compatibility of LD_AUDIT interface?
- From: Ben Woodard <woodard at redhat dot com>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: "Carlos O'Donell" <carlos at redhat dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Fri, 20 Mar 2015 11:11:21 -0700
- Subject: Re: What does LAV_CURRENT mean backwards compatibility of LD_AUDIT interface?
- Authentication-results: sourceware.org; auth=none
- References: <54EFBC96 dot 7010608 at redhat dot com> <5507BE70 dot 4090800 at redhat dot com> <20150318215629 dot 2BA1D2C3B30 at topped-with-meat dot com> <550A1A30 dot 2020500 at redhat dot com> <20150319192738 dot D24212C3B11 at topped-with-meat dot com> <550B8F0A dot 80006 at redhat dot com> <20150320170508 dot 5CCBC2C3B82 at topped-with-meat dot com>
> On Mar 20, 2015, at 10:05 AM, Roland McGrath <firstname.lastname@example.org> wrote:
>> The wording does seem to indicate that if ld.so says
>> it supports verion 2, that it must also support version 1.
> Agreed. But that's all in the realm of QoI since the module can't really
> tell the difference between an rtld that doesn't support its version
> because the version is too new from because the version is too old.
I personally feel like assuming that it also supports the previous versions is kind of straining at an interpretation but it will probably be practically true for the reasonable future â like the functional lifetime of ELF (which may out live all of us). Iâll clear it up when Iâm done with my patch which will include documentation.