All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin Walters <walters@verbum.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: magic libtool .la removal
Date: Tue, 18 Jun 2013 11:00:21 -0400	[thread overview]
Message-ID: <1371567621.3466.16.camel@localhost> (raw)
In-Reply-To: <CAJTo0LZD46Gckm=PGRw2NdSBibREWUzJbG_zhVtcAAqtAunn+w@mail.gmail.com>

On Tue, 2013-06-18 at 15:56 +0100, Burton, Ross wrote:

> I also remember discussion with Colin Walters about ostree, which at
> one point only removed from $libdir itself (my "libdir" argument) but
> now removes all .la files.  Colin, the commit that changed the la
> killing to recurse didn't have a rationale - can you clarify this?  If
> ostree can get away with removing all, them maybe we don't need the
> "libdir" option at all.

The relevant data I have on hand are:

https://bugzilla.gnome.org/show_bug.cgi?id=654013
https://git.gnome.org/browse/jhbuild/commit/?id=965c8d5ceda9d1c5d6021ef2c534e0a7f68ca976

I think the executive summary is that libltdl knows how to load .so
files directly (at least currently), so there's no reason to have even
${libdir}/modulename/plugins/foo.la.





  reply	other threads:[~2013-06-18 15:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 14:31 RFC: magic libtool .la removal Burton, Ross
2013-06-18 14:42 ` Phil Blundell
2013-06-18 14:56   ` Burton, Ross
2013-06-18 15:00     ` Colin Walters [this message]
2013-06-18 15:05       ` Burton, Ross
2013-06-18 15:47         ` Richard Purdie
2013-06-18 15:52           ` Burton, Ross
2013-06-18 15:54           ` Phil Blundell
2013-06-18 15:59             ` Burton, Ross
2013-06-18 16:05           ` Colin Walters
2013-06-18 16:39             ` Colin Walters

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=1371567621.3466.16.camel@localhost \
    --to=walters@verbum.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.