From: Mario Domenech Goulart <mario@ossystems.com.br>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] libxml2: explicitly disable zlib for native builds
Date: Thu, 21 Aug 2014 12:11:03 +0000 [thread overview]
Message-ID: <87oave11rc.fsf@parenteses.org> (raw)
In-Reply-To: <1408607451.1669.109.camel@ted> (Richard Purdie's message of "Thu, 21 Aug 2014 08:50:51 +0100")
On Thu, 21 Aug 2014 08:50:51 +0100 Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
> On Thu, 2014-08-14 at 17:20 -0300, Mario Domenech Goulart wrote:
>> Without this change, meta-openembedded's php recipe (as of 45e62fb8 --
>> "php 5.4.14: use pkg-config for libxml2 detection") breaks with this
>> error on my system:
>>
>> tmp/sysroots/x86_64-linux/usr/lib/libxml2.so: undefined reference
>> to `gzopen64@ZLIB_1.2.3.3'
>>
>> It seems that the host's zlib is leaking into libxml2's build.
>
> It turns out we need a zlib dependency here, else createrepo fails to
> deal with the compressed index files in the rpm repos. With rpm enabled,
> you can reproduce with:
>
> "bitbake package-index"
>
> Unfortunately this error causes a cascade of other problems and caused
> several people hours of work trying to figure out why the autobuilder
> was "exploding".
>
> Basically, the error above triggers a binary character to be emitted
> into the logs. The error reporting tool chokes on this since JSON can't
> handle the character causing an exception deep in the event handling
> code.
>
> That exception is badly handled and causes bitbake to enter an infinite
> loop, spewing traceback data to the console. That in turn creates
> gigabytes of log files and the autobuilder falls over.
>
> So if anyone wonders why we haven't had patches merging, this is why.
> We're now quite behind with the queue.
>
> Obviously there are fixes to make in multiple parts of the system to
> stop this kind of error escalating so badly again.
Oh, boy. I'm really sorry for all the trouble this apparently innocent
patch caused. Unfortunately we didn't catch this issue here, as we
don't use rpm.
Thanks for all the work you guys have put into handling this issue.
I'll try to come up with a better patch.
Best wishes.
Mario
--
http://www.ossystems.com.br
prev parent reply other threads:[~2014-08-21 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 20:20 [PATCH] libxml2: explicitly disable zlib for native builds Mario Domenech Goulart
2014-08-21 7:50 ` Richard Purdie
2014-08-21 12:00 ` Otavio Salvador
2014-08-21 12:11 ` Mario Domenech Goulart [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=87oave11rc.fsf@parenteses.org \
--to=mario@ossystems.com.br \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--cc=richard.purdie@linuxfoundation.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