From: "Clément Chigot" <chigot@adacore.com>
To: Howard Chu <hyc@symas.com>, Michael Matz <matz@suse.de>
Cc: binutils@sourceware.org
Subject: Re: [RFC] Move static archive dependencies into ld
Date: Thu, 13 Apr 2023 11:10:46 +0200 [thread overview]
Message-ID: <CAJ307EgxOe0Sbt=+gpqpbiemUMmt94ShgJDQDv0J1QTeAu2BqA@mail.gmail.com> (raw)
In-Reply-To: <3b124775-aa86-7e29-eba4-fbf07ffa0819@symas.com>
On Fri, Feb 17, 2023 at 9:53 PM Howard Chu <hyc@symas.com> wrote:
>
> Michael Matz via Binutils wrote:
> > Hello,
> >
> > this is an RFC for now. When met with some acceptance I'll cobble up a
> > similar thing for gold as well and then make the libdep.so plugin only
> > emit a warning message that its functionality is obsoleted and moved
> > into ld itself. As Cary put it back in 2020 when the plugin was added:
> >
> > ( https://sourceware.org/pipermail/binutils/2020-December/114536.html )
> >
> > "Did I miss any discussion about whether this feature should/could be
> > implemented directly in the linkers, rather than via a plugin? I
> > wouldn't be opposed to it."
>
> I'm all for it. I went the plugin route initially because it seemed the
> easiest way to get the feature written and accepted but I agree with you,
> it'd be much more useful if it was implicitly supported by default.
I do support this feature as well.
As seen recently, the plugin is not correctly built when shared
support is disabled. It means that a feature made to enhance static
support does not work when only static support is available...
I was planning to disable its creation (see [1]) because of potential
harmful side effects on Windows.
But this solution is far better.
Thanks Chu for pointing it out to me.
[1] https://sourceware.org/pipermail/binutils/2023-April/127045.html
Thanks,
Clément
next prev parent reply other threads:[~2023-04-13 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 15:03 Michael Matz
2023-02-17 20:53 ` Howard Chu
2023-04-13 9:10 ` Clément Chigot [this message]
2023-06-05 14:16 ` Howard Chu
2023-06-05 15:32 ` Michael Matz
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='CAJ307EgxOe0Sbt=+gpqpbiemUMmt94ShgJDQDv0J1QTeAu2BqA@mail.gmail.com' \
--to=chigot@adacore.com \
--cc=binutils@sourceware.org \
--cc=hyc@symas.com \
--cc=matz@suse.de \
/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).