From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] perl: strip RPATH from libxml-parser-perl Expat.so
Date: Thu, 24 Jul 2014 22:33:30 -0300 [thread overview]
Message-ID: <53D1B3EA.10409@gmail.com> (raw)
In-Reply-To: <1405601460.3668.17.camel@ted>
Hi,
On 17-07-2014 09:51, Richard Purdie wrote:
> First we need to understand the problem exactly. Do you have a
> reproducer that always works?
This happens on daisy. And my test case was:
1) add meta-intel and meta-crownbay layers
2) build MACHINE=qemux86 bitbake libxml-parser-perl
3) build MACHINE=genericx86 bitbake libxml-parser-perl
4) build MACHINE=crownbay-noemgd bitbake libxml-parser-perl
The step 4 wont complete because rpath issues.
To get it work:
MACHINE=crownbay-noemgd bitbake libxml-parser-perl perl -c cleanssate
Then
MACHINE=crownbay-noemgd bitbake libxml-parser-perl
Until now master is not affected.
I am working to fix the libxml-parser-perl
(http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=joaohf/daisy-libxml-parser-perl-rpath).
But I am not sure if it solves the root problem. Because OE should build
using three differents MACHINEs using the same workdir, sstate-cache.
Thanks.
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
prev parent reply other threads:[~2014-07-25 1:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 22:48 [PATCH] perl: strip RPATH from libxml-parser-perl Expat.so Paul Gortmaker
2014-06-19 13:26 ` Koen Kooi
2014-07-16 3:00 ` João Henrique Ferreira de Freitas
2014-07-16 8:33 ` Richard Purdie
2014-07-17 1:12 ` João Henrique Ferreira de Freitas
2014-07-17 12:51 ` Richard Purdie
2014-07-25 1:33 ` João Henrique Ferreira de Freitas [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=53D1B3EA.10409@gmail.com \
--to=joaohf@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--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 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.