All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burton, Ross" <ross.burton@intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: RFC: Separate build dir for autotools
Date: Tue, 25 Feb 2014 18:43:51 +0000	[thread overview]
Message-ID: <CAJTo0LY=TinUmQ+=d0_3oc97OwZNpw4yghfvbztyVF3EcJuteQ@mail.gmail.com> (raw)
In-Reply-To: <CAP71Wjxz0e7qzU4tVZ3XEpF1oZtCErqjD4pPnETVJLnoecq3QQ@mail.gmail.com>

On 25 February 2014 17:36, Nicolas Dechesne <nicolas.dechesne@linaro.org> wrote:
> right. I have recently (on dora) noticed that mesa build is broken
> when using separate build dir, i have the following extra config:
>
> PACKAGECONFIG_append = " gallium gallium-egl gallium-gbm gallium-llvm"
>
> since gallium-egl needs the egl.h files generated during mesa build.
> the generated files stay in $B while gallium-egl is looking for them
> in $S (or sysroot)

Pretty sure I fixed that:  oe-core fbc7092f0ae07538d4363679b1597ba4e556d1a8

It looks like that's in Dora so we've possibly regressed again, can
you file a bug (CCing me) with the build log?

Ross


  reply	other threads:[~2014-02-25 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 14:58 RFC: Separate build dir for autotools Richard Purdie
2014-02-24 15:06 ` Otavio Salvador
2014-02-24 15:27 ` Martin Jansa
2014-02-24 15:41   ` Burton, Ross
2014-02-24 16:09     ` Martin Jansa
2014-02-24 16:27       ` Richard Purdie
2014-02-26 19:11         ` Martin Jansa
2014-02-26 19:54           ` Burton, Ross
2014-02-26 20:20             ` Phil Blundell
2014-02-25 17:36       ` Nicolas Dechesne
2014-02-25 18:43         ` Burton, Ross [this message]
2014-02-25 22:10           ` Nicolas Dechesne
2014-02-26 10:58             ` Nicolas Dechesne
2014-02-25  5:46 ` Khem Raj
2014-02-25  9:52   ` Burton, Ross
2014-02-25 16:32     ` Khem Raj

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='CAJTo0LY=TinUmQ+=d0_3oc97OwZNpw4yghfvbztyVF3EcJuteQ@mail.gmail.com' \
    --to=ross.burton@intel.com \
    --cc=nicolas.dechesne@linaro.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 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.