This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Resend: Add a new chapter on the dynamic linker
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Ben Woodard <woodard at redhat dot com>
- Cc: <libc-alpha at sourceware dot org>, Carlos O'Donell <codonell at redhat dot com>, <fwiemer at redhat dot com>, <ricaljasan at pacific dot net>
- Date: Fri, 13 Oct 2017 22:39:49 +0000
- Subject: Re: [PATCH] Resend: Add a new chapter on the dynamic linker
- Authentication-results: sourceware.org; auth=none
- References: <20171012215658.8524-1-woodard@redhat.com> <alpine.DEB.2.20.1710122216080.4373@digraph.polyomino.org.uk> <CABG5n3C=WKvFrQDn5jgcOqz91-UK5BR_SKnkKiuAKRR9bY9cVA@mail.gmail.com>
On Fri, 13 Oct 2017, Ben Woodard wrote:
> > > +outside of a particular compilation unit. If you link object files
> > > +then the linker is able to find the location of referenced symbols or
> > > +functions in other compilation unit's object files, insert them into
> >
> > "units'", as you're referring to the object files of multiple compilation
> > units.
> >
>
> I don't think that you are correct about this. I intended it to be a
> possessive not a plural.
I was reading it as a possessive of a plural that ends with s (so needing
the apostrophe after the s, not before). If it were the possessive of a
singular compilation unit, I'd expect e.g. "another" in place of "other".
> > > +Libraries are a special kind object file which include the partially
> >
> > "kind of object file".
> >
> > > +linked aggregation of many compilation unit's object files. You can
> >
> > "units'".
> >
>
> See above. Possessive.
Again, possessive of plural (here it seems clear it's possessive of a
plural not a singular compilation unit, given the "many").
> > > +to run the executable. The shared libraries needed by am executable or
> >
> > "an executable".
> >
>
> I disagree with this change. It breaks the agreement between the subject
> and the object
I'm correcting the "am executable".
> I'm not sure what macros exist for different OSs that make use of glibc and
> how much I can say here that applies to everything. Are you saying $ORIGIN
> is universal? Are there more things are and need documenting?
$ORIGIN is nothing to do with the operating system. It's implemented in
OS-independent code in glibc, not in OS-specific code (though OS-specific
glibc code should still be documented in the glibc manual) and not in the
kernel. Likewise $PLATFORM and $LIB. (The setting of dl_platform values
is generally architecture-specific not OS-specific.)
--
Joseph S. Myers
joseph@codesourcery.com