From: Ian Lance Taylor <iant@google.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: PATCH/RFC: ld add -p/-P options
Date: Mon, 31 Aug 2009 17:43:00 -0000 [thread overview]
Message-ID: <m3d46bsxks.fsf@google.com> (raw)
In-Reply-To: <8ba6bed40908290341t46a3af19w38434d3d76722548@mail.gmail.com> (Matt Rice's message of "Sat\, 29 Aug 2009 03\:41\:18 -0700")
Matt Rice <ratmice@gmail.com> writes:
> ok, so here is the list of questions I have regarding -P/-p i couldn't
> glean from suns documentation
>
> a) does it require that the shared library denoted as the argument
> even exist, or does it just encode it as a shared library name which
> is assumed to exist at runtime?
The best way to answer all of these questions is to see what Solaris ld
actually does.
That said, I don't see any reason that the libraries must exist at link
time.
> b) if the library does exist does it use the soname encoded into the audit lib?
I assume so.
> c) in the testsuite i had to link to -ptmpdir/audit.so and
> -Ptmpdir/audit.so are these basename'd or as is specified on the
> command line?
I assume as specific on the command line if there is no soname.
> d) does ld do any searching for the audit library in the /lib/secure,
> /usr/lib/secure,/lib/secure/64 and /usr/lib/secure/64 directories or
> anywhere, or is this only handled at runtime?
I doubt it ld would search those directories by default, but I really
don't know.
> e) out of curiosity if 'a' is true does this mean an audit library
> could potentially audit itself when also being linked to in a
> DT_NEEDED?
I don't see why not.
Ian
next prev parent reply other threads:[~2009-08-31 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 21:41 Matt Rice
2009-08-30 2:30 ` Matt Rice
2009-08-31 17:43 ` Ian Lance Taylor [this message]
2009-09-12 15:21 ` Matt Rice
2009-09-12 16:56 ` Matt Rice
2009-09-14 0:42 ` Alan Modra
2009-09-14 0:39 ` Alan Modra
2009-09-14 11:59 ` Matt Rice
2009-09-22 20:50 ` Matt Rice
2009-09-23 13:56 ` Alan Modra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d46bsxks.fsf@google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=ratmice@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).