From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: yocto@yoctoproject.org
Subject: Re: Help needed understanding do_rootfs error
Date: Fri, 15 Jun 2012 07:01:57 +0100 [thread overview]
Message-ID: <4FDACFD5.4020808@r-finger.com> (raw)
In-Reply-To: <3AD32D08-64C8-4F37-BF50-9D08560D0194@keylevel.com>
Hi,
On 14/06/12 22:42, Chris Tapp wrote:
> On 14 Jun 2012, at 21:44, Chris Tapp wrote:
>
>> The log for do_rootfs is showing: < snip > error: Failed
>> dependencies: libGL.so.1 is needed by libglut3-7.11-r13.2.armv6
>> libGL.so.1 is needed by column-wallboard-1.0-r1.armv6 libGL.so.1 is
>> needed by libglu1-7.11-r13.2.armv6
>>
>> libGL is showing in the work area, so I think I just need to add a
>> dependency. But what and where?
There should be no GL on RPI at all, the HW drivers only support GLES/2,
so the short answer is you can't pull in packages that require GL (in
theory you could build mesa with the software rasterizer, but you will
get unacceptable performance, and in the presence of GLES2 that makes no
sense anyway).
Incidentally, the GLES libs are not currently packaged by
meta-raspberrypi, I submitted a pull request for this yesterday.
> Ah, there was an ERROR right at the start of the build saying there
> were multiple providers for virtual/libgl (mesa-xlib, mesa-dri). How
> can I track down the cause of this? Building virtual/libgl doesn't
> get this error - it only shows when I build the full image.
In general, mesa-xlib provides a software GLX emulation, mesa-dri
provides glx based on the GLX extension and each machine conf needs to
choose a preferred provider for virtual/libgl to get rid of this error.
However, in the RPI case, no virtual/libgl should be getting pulled into
the images.
Tomas
next prev parent reply other threads:[~2012-06-15 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 20:44 Help needed understanding do_rootfs error Chris Tapp
2012-06-14 21:42 ` Chris Tapp
2012-06-15 6:01 ` Tomas Frydrych [this message]
2012-06-15 20:09 ` Chris Tapp
2012-06-16 9:09 ` Tomas Frydrych
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=4FDACFD5.4020808@r-finger.com \
--to=tf+lists.yocto@r-finger.com \
--cc=yocto@yoctoproject.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.