From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
Poky <poky@yoctoproject.org>,
Otavio Salvador <otavio@ossystems.com.br>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] xorg-driver-common: Add configure and install appends from meta-intel
Date: Thu, 05 Sep 2013 13:14:49 +0100 [thread overview]
Message-ID: <1378383289.32427.63.camel@ted> (raw)
In-Reply-To: <CAJTo0Labk000SpLOiM8gtuSu2pwK0jsgU9osO60GEFntThxSeA@mail.gmail.com>
On Thu, 2013-09-05 at 12:40 +0100, Burton, Ross wrote:
> On 5 September 2013 12:37, Otavio Salvador <otavio@ossystems.com.br> wrote:
> >> Sadly when using libtool you can't "opt-out" of installing .la files
> >> unless you delete the files that just got installed. In my opinion
> >> this is something that needs to be done globally instead of
> >> per-recipe.
> >
> > So autotools.bbclass?
>
> Exactly. Phil sent patches to do this previously, and I've a
> branch... somewhere that has another unfinished version.
I continue to have mixed feelings about this:
* We've not done side by side build comparisons with something like
buildhistory.
* Figuring out any runtime issues with dlopen is the hardest part and we
don't actually have real data on whether there are issues there or not.
* We'd be deviating from the way the libtool authors suggest their tool
should operate. This makes filing bug reports and interacting with
upstream harder. I continue to dream of a libtool with working sysroot
support for example instead of carrying our hacks/workarounds/bugfixes.
* They are used in places, for example the darwin shlibs code currently
uses them. It could be updated to use otool these days mind but I'd
probably make the current code a fallback for unknown arches since it is
guaranteed to work everywhere.
So whilst I know several people love to just delete them, its a slightly
more complex issue than that.
Cheers,
Richard (who isn't keen on libtool and would rather replace that instead)
next prev parent reply other threads:[~2013-09-05 12:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 0:18 [PATCH 0/4] Updates in support of genericx86* Darren Hart
2013-09-05 0:18 ` [PATCH 1/4] linux-firmware: Update SRCREV, pull in iwlwifi-7260 support Darren Hart
2013-09-05 1:04 ` Otavio Salvador
2013-09-05 3:34 ` Darren Hart
2013-09-05 6:57 ` [poky] " Saul Wold
2013-09-05 8:50 ` Richard Purdie
2013-09-05 14:49 ` Darren Hart
2013-09-05 0:18 ` [PATCH 2/4] xorg-driver-common: Add configure and install appends from meta-intel Darren Hart
2013-09-05 0:54 ` Otavio Salvador
2013-09-05 3:33 ` Darren Hart
2013-09-05 9:53 ` Burton, Ross
2013-09-05 11:37 ` Otavio Salvador
2013-09-05 11:40 ` Burton, Ross
2013-09-05 12:14 ` Richard Purdie [this message]
2013-09-05 12:23 ` Phil Blundell
2013-09-05 13:48 ` Burton, Ross
2013-09-05 15:32 ` Richard Purdie
2013-09-05 16:23 ` Burton, Ross
2013-09-05 15:00 ` Darren Hart
2013-09-05 0:18 ` [PATCH 3/4] xf86-video-mga: Pull in Matrox MGA support " Darren Hart
2013-09-05 9:57 ` Burton, Ross
2013-09-05 13:04 ` Tom Zanussi
2013-09-05 14:52 ` Darren Hart
2013-09-05 15:11 ` Burton, Ross
2013-09-05 15:21 ` Burton, Ross
[not found] ` <5229303F.1090209@windriver.com>
2013-09-10 2:37 ` Darren Hart
[not found] ` <522E9996.8000107@windriver.com>
2013-09-10 17:54 ` Darren Hart
2013-09-05 0:18 ` [PATCH 4/4] genericx86: Create a x86-common.inc base for the x86 BSPs Darren Hart
2013-09-05 1:16 ` [PATCH 0/4] Updates in support of genericx86* Otavio Salvador
2013-09-05 3:35 ` Darren Hart
2013-09-05 9:47 ` [poky] " Burton, Ross
2013-09-05 11:06 ` Richard Purdie
2013-09-05 11:40 ` Otavio Salvador
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=1378383289.32427.63.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=poky@yoctoproject.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