From: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
To: "Burton\, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pango: add libpcre to DEPENDS
Date: Fri, 09 Sep 2016 12:32:31 +0300 [thread overview]
Message-ID: <871t0tzads.fsf@ni.com> (raw)
In-Reply-To: <CAJTo0LY_6wg10ft-RNRrYH7xa93=aWB9LuH=gxEpgf19vC446Q@mail.gmail.com>
On Thu, 08 Sep 2016, "Burton, Ross" <ross.burton@intel.com> wrote:
> On 8 September 2016 at 11:37, Ioan-Adrian Ratiu <adrian.ratiu@ni.com> wrote:
>
>> No. It fails sporadically on the jenkins build machine when it's under
>> load. Somehow adding the pcre dependency directly to pango fixes the
>> build machine which is really weird. I can't replicate this on my dev
>> machine.
>>
>
> Can you get access to the build directory when it fails? It would be
> interesting to see what ldd says the gen-all-unicode is linking to.
I cleared the build directory and sstate cache, started with a clean
rebuild and I can't reproduce the error anymore. gen-all-unicode is
built as expected and at runtime it links with libpcre as expected
and the build succeeds. This is really weird, I didn't touch these
packages at all, they just sporadically failed out of the blue and now
they work.
>
> Ross
next prev parent reply other threads:[~2016-09-09 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 9:56 [PATCH] pango: add libpcre to DEPENDS Ioan-Adrian Ratiu
2016-09-08 10:14 ` Burton, Ross
2016-09-08 10:37 ` Ioan-Adrian Ratiu
2016-09-08 10:39 ` Burton, Ross
2016-09-09 9:32 ` Ioan-Adrian Ratiu [this message]
2016-09-09 9:36 ` Burton, Ross
2016-10-05 10:46 ` Ioan-Adrian Ratiu
2016-10-05 11:59 ` Ioan-Adrian Ratiu
2016-10-05 13:55 ` Burton, Ross
2016-10-05 14:39 ` Ioan-Adrian Ratiu
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=871t0tzads.fsf@ni.com \
--to=adrian.ratiu@ni.com \
--cc=openembedded-core@lists.openembedded.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