From: Phil Blundell <philb@gnu.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC PATCH] autotools: Don't install .la files if the distro doesn't want them
Date: Wed, 28 Nov 2012 15:15:29 +0000 [thread overview]
Message-ID: <1354115731.23886.94.camel@phil-desktop> (raw)
In-Reply-To: <CAJTo0LYHS+j4s_=+2t1v7yXQ6tPxkStOwMJUsAOy9U3BXoN2SA@mail.gmail.com>
On Wed, 2012-11-28 at 15:09 +0000, Burton, Ross wrote:
> On 17 October 2012 14:42, Phil Blundell <philb@gnu.org> wrote:
> > It's not obvious that libtool's .la files serve any very useful purpose
> > on a modern system and they can be positively vexatious under some
> > circumstances. Make installation of this stuff conditional on the new
> > "libtool-garbage" flag in DISTRO_FEATURES and backfill it for existing
> > distros.
>
> I never saw a patch with a less inflammatory (albeit accurate) name.
> Libtool has been causing me pain again so I'd love to turn this on.
> Is this still good for merging with a different name (libtool-la?)
The only minor roadblock to this is that RP wasn't very keen on the
clean-on-reconfigure patch when I submitted that one independently, see:
http://lists.linuxtogo.org/pipermail/openembedded-core/2012-October/031449.html
Without some equivalent of that thing, turning off .la files in an
existing build tree will cause you to start getting failures. I guess
we could just accept that as an occupational hazard, and say that people
who turn off libtool-la need to take care of the necessary cleaning for
themselves.
Other than that, yes, I would also like to see this patch get merged.
p.
prev parent reply other threads:[~2012-11-28 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-17 13:42 [RFC PATCH] autotools: Don't install .la files if the distro doesn't want them Phil Blundell
2012-10-17 13:47 ` Burton, Ross
2012-10-17 16:38 ` Phil Blundell
2012-10-17 13:51 ` Paul Eggleton
2012-11-28 15:09 ` Burton, Ross
2012-11-28 15:15 ` Phil Blundell [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=1354115731.23886.94.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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