From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Build failures due zlib problem
Date: Wed, 21 Mar 2012 16:55:02 +0000 [thread overview]
Message-ID: <1332348902.9740.175.camel@ted> (raw)
In-Reply-To: <1332323639.9740.125.camel@ted>
On Wed, 2012-03-21 at 09:53 +0000, Richard Purdie wrote:
> On Tue, 2012-03-20 at 22:40 -0300, Otavio Salvador wrote:
> > | NOTE: Unpacking
> > /home/ostt-devel/src/embedded-systems/downloads/gcc-4_6-branch_gcc.gnu.org_.svn.gcc.branches_184847_.tar.gz
> > to /home/ostt-devel/src/embedded-systems/tmp-eglibc-eglibc/work-shared/gcc-4.6.3+svnr184847-r28/
> > | gzip: /usr/lib/libz.so.1: version `ZLIB_1.2.5.1' not found (required by gzip)
> > | tar: Child returned status 1
> >
> > Does anyone sees it? Our autobuilder is failing this way.
>
> Yes, its being seen. I think its appeared after the pigz-native change
> but it exposes an underlying problem.
>
> The issue is that we have a gzip binary in the sysroot linking against
> libz. We can get into a situation where we remove libz to rebuild but we
> don't remove the gzip binary yet.
>
> gzip-native is a tricky one since its one of those recipes we don't
> correctly have a dependency chain for and is also implied in
> ASSUME_PROVIDED (else how to we extract tarballs?).
>
> Whilst I've implicated pigz-native, we could potentially see this with
> gzip-native too, I'd guess its just more flexible about the libz symbols
> it uses.
>
> I'm trying to come up with a good way of handling this but at the moment
> I'm drawing a blank for a neat solution :(.
>
> Something along the lines of perl-native might be necessary. We could
> also decide its a special case and remove gzip whenever libz is
> removed...
I've pushed a couple of fixes in this area which should help.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-21 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 1:40 Build failures due zlib problem Otavio Salvador
2012-03-21 9:53 ` Richard Purdie
2012-03-21 16:55 ` Richard Purdie [this message]
2012-03-22 17:12 ` Otavio Salvador
2012-03-21 17:50 ` McClintock Matthew-B29882
2012-03-21 19:53 ` Denys Dmytriyenko
2012-03-21 22:40 ` Richard Purdie
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=1332348902.9740.175.camel@ted \
--to=richard.purdie@linuxfoundation.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