From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Master plan for fixing elibtoolize
Date: Wed, 22 Mar 2017 10:38:01 +0100 [thread overview]
Message-ID: <20170322103801.116a5884@gentoo.org> (raw)
In-Reply-To: <20170318192936.GI25144@stuge.se>
On Sat, 18 Mar 2017 19:29:36 +0000
Peter Stuge <peter@stuge.se> wrote:
> Alexis Ballier wrote:
> > > If elibtoolize results in different binaries being produced, then
> > > it's done wrong in the first place. AFAIU the primary goal of
> > > elibtoolize logic is to fix issues on recent systems with
> > > outdated build systems. Which is certainly not something that
> > > needs to be done for every user out there.
> >
> > You probably didn't have a look at what the patches fix. Having a
> > quick look at patches there,
>
> Where are those patches you mention?
Those in ELT-patches...
> > I could fine one fixing relink to old libs (from / instead of $D),
>
> I have an open bug for this for a package, both in Gentoo and
> upstream. It seems to be a problem with libtool itself, is that
> about right?
With recent libtools it is most likely to be the package's fault, like
wrong/poor usage of autotools.
> > another one fixing parallel install. The former produces broken
> > binaries, the latter none at all.
> >
> > I seriously doubt this shouldn't be fixed for every user.
>
> What "this" do you refer to? Sorry for the confusion, I want to
> understand.
the bugs
prev parent reply other threads:[~2017-03-22 9:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 17:14 [gentoo-dev] [RFC] Master plan for fixing elibtoolize Michał Górny
2017-03-17 17:17 ` Alexis Ballier
2017-03-17 23:38 ` James Le Cuirot
2017-03-18 6:53 ` Michał Górny
2017-03-18 10:18 ` Alexis Ballier
2017-03-18 10:21 ` Michał Górny
2017-03-18 10:31 ` Alexis Ballier
2017-03-18 19:29 ` Peter Stuge
2017-03-22 9:38 ` Alexis Ballier [this message]
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=20170322103801.116a5884@gentoo.org \
--to=aballier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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