From: Valentin Popa <valentin.popa@intel.com>
To: Robert Yang <liezhi.yang@windriver.com>,
Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [dora][regression] mesa failed to build
Date: Mon, 07 Apr 2014 17:55:00 +0300 [thread overview]
Message-ID: <5342BC44.2000708@intel.com> (raw)
In-Reply-To: <533F8B7C.8010409@windriver.com>
Indeed the build failure was introduced by that patch, which enters a
logical conflict with the bbappend file for mesa.
To remain compatible with the future releases I suggest to not
remove/add flags from/to EXTRA_OECONF explicitly, and make use of what
PACKAGECONFIG contains.
The first part of the __anonymous function from the bbappend file can be
simply replaced with:
PACKAGECONFIG_remove = "egl"
and the second part with:
PROVIDES_remove = "virtual/libgles1 virtual/libgles2 virtual/egl"
and
PROVIDES_remove = "virtual/libgl" if mx6 is in SOC_FAMILY.
On 04/05/2014 07:50 AM, Robert Yang wrote:
>
> Yes, seems related to the following one, add Valentin Popa in the loop:
>
> commit bcfbddd8fa9760f681d7366c8d507fd0bef3a854
> Author: Valentin Popa <valentin.popa@intel.com>
> Date: Thu Feb 27 11:51:17 2014 +0200
>
> mesa: build fix for gallium-egl
>
> // Robert
>
> On 04/05/2014 12:38 PM, Otavio Salvador wrote:
>> Hello,
>>
>> In one of our custom BSPs we saw a build failure in mesa:
>>
>> | make[1]: Leaving directory
>> `.../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/build'
>>
>> | sed: can't read
>> .../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/image/usr/include/EGL/eglplatform.h:
>>
>> No such file or directory
>> | WARNING: exit code 2 from a shell command.
>> | ERROR: Function failed: do_install (log file is located at
>> .../build/tmp/work/cortexa9hf-vfp-neon-mx6-oel-linux-gnueabi/mesa/2_9.1.6-r0/temp/log.do_install.17155)
>>
>> recipe mesa-2_9.1.6-r0: task do_install: Failed
>> ERROR: Task 2643
>> (.../sources/poky/meta/recipes-graphics/mesa/mesa_9.1.6.bb,
>> do_install) failed with exit code '1'
>> recipe gnutls-2.12.23-r8.4: task do_configure: Succeeded
>>
>> This seems not related to the bbappend we have in meta-fsl-arm[1], in
>> Dora. I think this came in today's changes in the branch.
>>
>> 1.
>> http://git.yoctoproject.org/cgit/cgit.cgi/meta-fsl-arm/tree/recipes-graphics/mesa/mesa_9.1.6.bbappend?h=dora
>>
>> This builder has PRServer enabled.
>>
>> As I am going to be traveling so won't have time to debug this bug I
>> preferred to report it so someone can debug.
>>
next prev parent reply other threads:[~2014-04-07 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 4:38 [dora][regression] mesa failed to build Otavio Salvador
2014-04-05 4:50 ` Robert Yang
2014-04-07 14:55 ` Valentin Popa [this message]
2014-04-09 3:13 ` Robert Yang
2014-04-11 13:56 ` Otavio Salvador
2014-04-11 13:56 ` [OE-core] " Otavio Salvador
2014-04-12 3:33 ` Robert Yang
2014-04-14 8:35 ` Valentin Popa
[not found] <5343D6BB.2000104@u-mobo.com>
2014-04-08 11:13 ` Pierluigi Passaro
2014-04-08 12:12 ` Ronaldo Nunez
2014-04-08 16:06 ` Pierluigi Passaro
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=5342BC44.2000708@intel.com \
--to=valentin.popa@intel.com \
--cc=liezhi.yang@windriver.com \
--cc=meta-freescale@yoctoproject.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@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.