From: Valentin Popa <valentin.popa@intel.com>
To: Robert Yang <liezhi.yang@windriver.com>,
Otavio Salvador <otavio@ossystems.com.br>,
Richard Purdie <richard.purdie@linuxfoundation.org>
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, 14 Apr 2014 11:35:41 +0300 [thread overview]
Message-ID: <534B9DDD.4060403@intel.com> (raw)
In-Reply-To: <5348B401.20908@windriver.com>
On 04/12/2014 06:33 AM, Robert Yang wrote:
>
>
> On 04/11/2014 09:56 PM, Otavio Salvador wrote:
>> Hello,
>>
>> On Wed, Apr 9, 2014 at 12:13 AM, Robert Yang
>> <liezhi.yang@windriver.com> wrote:
>>> On 04/07/2014 10:55 PM, Valentin Popa wrote:
>>>> 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.
>>>>
>>>
>>> Hi Otavio,
>>>
>>> Does Valentin's suggestions work for you, please?
>>
>> I am traveling and won't be able to test it.
>>
>> However I am quite surprise this didn't come out /before/ when the
>> dora updates were in test in AB since meta-fsl-arm is tested in AB
>> too. We need to figure /why/ this broke and for now I think we ought
>> to revert this dora patch.
>>
>> This kind of change needs to be coordinated and raise a build break in
>> an Yocto Project is unacceptable IMO.
>>
>> For me it is clear this didn't run in AB before merging. :(
>>
>
> I'm sorry about that, I had run it on my *local* AB before merging, but
> the local AB is less powerful and doesn't include the meta-fsl-arm layer,
> I'm fine to revert it, what's RP and valentin's opinion, please ?
>
> // Robert
>
>
>
I'll send a patch to handle this special case for meta-fsl-arm (mutate
eglplatform.h only if it exists)
prev parent reply other threads:[~2014-04-14 8:35 UTC|newest]
Thread overview: 7+ 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
2014-04-09 3:13 ` Robert Yang
2014-04-11 13:56 ` Otavio Salvador
2014-04-12 3:33 ` Robert Yang
2014-04-14 8:35 ` Valentin Popa [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=534B9DDD.4060403@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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox