This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: What does LAV_CURRENT mean backwards compatibility of LD_AUDIT interface?
- From: Roland McGrath <roland at hack dot frob dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>, Ben Woodard <woodard at redhat dot com>
- Date: Fri, 20 Mar 2015 10:05:08 -0700 (PDT)
- 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>
> 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.