From: John Weber <rjohnweber@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 1/2] mesa: Update to follow OE-Core changes
Date: Sat, 22 Feb 2014 13:32:19 -0600 [thread overview]
Message-ID: <5308FB43.5080406@gmail.com> (raw)
In-Reply-To: <CAP9ODKo8Ti2XVnKk+hymH7yDD-3VsVTvwsSuhSLai+2N9R3gng@mail.gmail.com>
Hi Otavio,
On 2/22/14, 11:46 AM, Otavio Salvador wrote:
> Hello John,
>
> On Sat, Feb 22, 2014 at 1:13 PM, John Weber <rjohnweber@gmail.com> wrote:
>> On 2/21/14, 3:54 PM, Otavio Salvador wrote:
>>> This updates the bbappend to the newer version; as mesa now provides
>>> the needed PACKAGECONFIG settings we rely on this instead of using an
>>> annonymous Python code to change it during build time.
>>>
>>> The bbappend file now is much easier to read.
>>
>> Thanks Otavio - I'm really glad you were able to free up some time to work
>> on this. As master changes, it's clear that it takes a lot of work to keep
>> up with it.
>>
>> I applied both patches and ran into a snag. I'm deleting the tmp and
>> rebuilding, but here is what I'm seeing:
>>
>> WARNING: libgl-mesa-9.2.5 was registered as shlib provider for libGL.so.1,
>> changing it to libgl-mx6-3.10.9-1.0.0-hfp because it was built later
>>
>> That is followed by a pretty unspecific error during the do_rootfs task.
>> Looking into the task log, this is the error that seems to indicate the
>> source of failure:
>>
>> error: file /usr/lib/libGL.so.1.2.0 conflicts between attempted installs of
>> libgl-mx6-3.10.9+1.0.0+hfp-r0.cortexa9hf_vfp_neon_mx6 and
>> libgl-mesa-9.2.5-r0.cortexa9hf_vfp_neon_mx6
> I must have missed this as I didn't spot this issue while testing.
> Please add following block of code below the bbappend and confirm it
> works for you.
>
> # FIXME: Dirty hack to allow use of Vivante GPU libGL binary
> do_install_append_mx6 () {
> rm -f ${D}${libdir}/libGL.*
> }
>
> Thanks for reporting this issue.
>
Thanks for helping to solve it. This fixed the issue with generating the
rootfs. Thanks!
next prev parent reply other threads:[~2014-02-22 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 21:54 [meta-fsl-arm][PATCH 0/2] Get master working again Otavio Salvador
2014-02-21 21:54 ` [meta-fsl-arm][PATCH 1/2] mesa: Update to follow OE-Core changes Otavio Salvador
2014-02-22 16:13 ` John Weber
2014-02-22 17:46 ` Otavio Salvador
2014-02-22 19:32 ` John Weber [this message]
2014-02-23 13:25 ` Otavio Salvador
2014-02-21 21:54 ` [meta-fsl-arm][PATCH 2/2] xserver-xorg: Backport 1.14.4 version Otavio Salvador
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=5308FB43.5080406@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.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.