From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libxml2: add missing dependency on binutils
Date: Tue, 21 Feb 2012 23:02:25 +0000 [thread overview]
Message-ID: <1329865345.2591.201.camel@x121e.pbcl.net> (raw)
In-Reply-To: <20120221224811.GB3769@jama.jama.net>
On Tue, 2012-02-21 at 23:48 +0100, Martin Jansa wrote:
> On Tue, Feb 21, 2012 at 02:26:49PM -0800, Steve Sakoman wrote:
> > I'll try a clean build to see if the problem persists. The libz
> > change from last week seems to have put my builds in a bad state, and
> > the PR bumps intended to fix things really don't seem to be fixing
> > things, at least on my build machines. I suspect it might be faster
> > to do a clean build than to track down where the corruption is.
>
> The list of PR bumped recipes probably wasn't complete for you. It was
> for me, but later I've noticed that ie subversion-1.6 wasn't bumped,
> because I'm using only 1.7.
>
> So it was complete for my default build (when those PR bumps were
> applied to all included layers at once, which is not the case for most
> people) and if you build different recipes or different versions you
> have to add your own PR bumps in those recipes (see khem's script).
>
> Clean build could be faster but doesn't fix installed -dev packages on
> target..
I still don't entirely understand why we don't just put libz.la back the
way it was. I can understand the attraction of eliminating .la files in
a general sense, but it doesn't seem as though the removal of this
particular one is buying us much. What is the reason for expending so
much effort on getting rid of it?
p.
next prev parent reply other threads:[~2012-02-21 23:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 19:07 [PATCH] libxml2: add missing dependency on binutils Steve Sakoman
2012-02-21 21:52 ` Richard Purdie
2012-02-21 22:26 ` Steve Sakoman
2012-02-21 22:48 ` Martin Jansa
2012-02-21 23:02 ` Phil Blundell [this message]
2012-02-22 15:09 ` Steve Sakoman
2012-02-21 22:58 ` Khem Raj
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=1329865345.2591.201.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.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