All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	Gary Thomas <gary@mlbassoc.com>
Subject: Re: Error building gdk-pixbuf-native
Date: Wed, 23 Sep 2015 23:25:46 +0100	[thread overview]
Message-ID: <1443047146.19044.43.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKpdpMK5jApg7cP3AQ70xEXoC3_V5i_mUGVqBVmTEcY-cw@mail.gmail.com>

On Tue, 2015-09-22 at 21:28 -0300, Otavio Salvador wrote:
> On Tue, Sep 22, 2015 at 8:30 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >
> >> On Sep 22, 2015, at 4:28 PM, Otavio Salvador <otavio.salvador@ossystems.com.br> wrote:
> >>
> >> On Tue, Sep 22, 2015 at 8:23 PM, Khem Raj <raj.khem@gmail.com> wrote:
> >>> its normal for build to use libraries from build host for native tools. If we want to abstract that
> >>> from host deps then creating a dependency on package-native is the way
> >>
> >> The point is this seems to be not deterministic. Sometimes this works,
> >> others it does not.
> >
> >
> > you can debug it by moving the dependency from default task to earlier or later task and see where its failing sometimes
> > some configure might run where we do not expect it to.
> 
> I cannot reproduce it locally, just in my autobuilder and now it does
> not fail anymore. Gary is the only one seeing it.

I think the way to reproduce this is to build gdk-pixbuf-native along
with harfbuzz-native and librsvg-native, then make a small change to the
gdk-pixbuf recipe that would cause it to rebuild, clean harfbuzz-native
and then build gdk-pixbuf.

I'm going to send out a patch which at least unblocked my own builds
when I ran into this locally.

Cheers,

Richard



  reply	other threads:[~2015-09-23 22:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 15:28 Error building gdk-pixbuf-native Gary Thomas
2015-09-22 18:05 ` Otavio Salvador
2015-09-22 18:14   ` Gary Thomas
2015-09-22 18:38     ` Otavio Salvador
2015-09-22 19:13       ` Gary Thomas
2015-09-22 20:52         ` Otavio Salvador
2015-09-22 23:23         ` Khem Raj
2015-09-22 23:28           ` Otavio Salvador
2015-09-22 23:30             ` Khem Raj
2015-09-23  0:28               ` Otavio Salvador
2015-09-23 22:25                 ` Richard Purdie [this message]
2015-09-23 12:15 ` Burton, Ross
2015-09-23 12:24   ` Gary Thomas

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=1443047146.19044.43.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gary@mlbassoc.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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.