From: Howard Chu <hyc@symas.com>
To: Marco Frigerio <marco.frigerio17@protonmail.com>,
"binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: usage of the libdep plugin of LD
Date: Mon, 13 Feb 2023 17:12:47 +0000 [thread overview]
Message-ID: <fe0638e2-283c-5935-32d8-e969abec589b@symas.com> (raw)
In-Reply-To: <z0Lr3_d8ZN9NWya8URdCDkWDrb9icc0uBryDMk-Xpif2QeFIcaPGP7YzeE23C7buzeXxxOh9Konq5CZkD-zNaFjKBHfPKpmRXYOTW-kMuPc=@protonmail.com>
Marco Frigerio via Binutils wrote:
> Hi,
> Is there a way of making sure that the libdep plugin of LD is used?
Not by default. You need to make sure ld is invoked with "-plugin .../libdep_plugin.so" yourself.
Easiest way might be a wrapper script.
>
> I have a static .a library with the __.LIBDEP section, but linking it to an executable raises linking errors.
>
> All the errors go away if I specify manually the same '-lXXX' which is written in __.LIBDEP, suggesting that the latter is ignored.
>
> GNU Binutils v 2.38, gcc 11.3.0, on Ubuntu Linux.
>
> I could not find anything in the man pages, and the LD docs (section 4) do not say anything about enabling/loading plugins.
>
> I hope this is the right place for this kind of questions, my apologies otherwise.
> Thanks
> - MF
>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
next prev parent reply other threads:[~2023-02-13 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 16:55 Marco Frigerio
2023-02-13 17:12 ` Howard Chu [this message]
2023-02-13 17:28 ` Howard Chu
2023-02-14 9:45 ` Marco Frigerio
2023-02-14 12:03 ` Nick Clifton
2023-02-13 17:13 ` Ulf Samuelsson
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=fe0638e2-283c-5935-32d8-e969abec589b@symas.com \
--to=hyc@symas.com \
--cc=binutils@sourceware.org \
--cc=marco.frigerio17@protonmail.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).