* Help needed understanding do_rootfs error @ 2012-06-14 20:44 Chris Tapp 2012-06-14 21:42 ` Chris Tapp 0 siblings, 1 reply; 5+ messages in thread From: Chris Tapp @ 2012-06-14 20:44 UTC (permalink / raw) To: Yocto Project The log for do_rootfs is showing: ERROR: Function failed: do_rootfs (see /media/SSD-RAID/build-denzil-pi/tmp/work/raspberrypi-poky-linux-gnueabi/sjs-x11-image-1.0-r0/temp/log.do_rootfs.8633 for further information) Generating solve db for /media/SSD-RAID/build-denzil-pi/tmp/deploy/rpm/raspberrypi... total: 1 0.000000 MB 1.252061 secs fingerprint: 1878 0.011180 MB 0.035400 secs install: 626 0.000000 MB 0.509277 secs dbadd: 626 0.000000 MB 0.498577 secs dbget: 2845 0.000000 MB 0.004722 secs dbput: 626 2.976128 MB 0.437150 secs readhdr: 6261 5.865680 MB 0.016813 secs hdrload: 3130 8.701488 MB 0.011505 secs hdrget: 112989 0.000000 MB 0.079470 secs Generating solve db for /media/SSD-RAID/build-denzil-pi/tmp/deploy/rpm/armv6-vfp... total: 1 0.000000 MB 10.453264 secs fingerprint: 15498 0.161164 MB 0.564440 secs install: 5166 0.000000 MB 4.552602 secs dbadd: 5166 0.000000 MB 4.466703 secs dbget: 51868 0.107568 MB 0.058265 secs dbput: 5166 25.200376 MB 3.996021 secs readhdr: 51661 50.213234 MB 0.411257 secs hdrload: 27384 81.464842 MB 0.083968 secs hdrget: 926377 0.000000 MB 0.500559 secs Generating solve db for /media/SSD-RAID/build-denzil-pi/tmp/deploy/rpm/all... total: 1 0.000000 MB 0.061929 secs fingerprint: 66 0.000926 MB 0.006248 secs install: 22 0.000000 MB 0.024989 secs dbadd: 22 0.000000 MB 0.023312 secs dbget: 186 0.000000 MB 0.000215 secs dbput: 22 0.103992 MB 0.010762 secs readhdr: 221 0.208192 MB 0.001765 secs hdrload: 113 0.315548 MB 0.000311 secs hdrget: 3236 0.000000 MB 0.001714 secs Generating solve db for /media/SSD-RAID/build-denzil-pi/tmp/deploy/rpm/all... total: 1 0.000000 MB 0.055491 secs fingerprint: 66 0.000926 MB 0.001160 secs install: 22 0.000000 MB 0.024206 secs dbadd: 22 0.000000 MB 0.022726 secs dbget: 186 0.000000 MB 0.000272 secs dbput: 22 0.103992 MB 0.011892 secs readhdr: 221 0.208192 MB 0.000313 secs hdrload: 113 0.315548 MB 0.000336 secs hdrget: 3236 0.000000 MB 0.002112 secs Processing task-core-boot... Processing dropbear... Processing task-core-x11-base... Processing task-core-ssh-dropbear... Processing task-x... 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? Chris Tapp opensource@keylevel.com www.keylevel.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed understanding do_rootfs error 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 0 siblings, 1 reply; 5+ messages in thread From: Chris Tapp @ 2012-06-14 21:42 UTC (permalink / raw) To: Yocto Project 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? 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. Chris Tapp opensource@keylevel.com www.keylevel.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed understanding do_rootfs error 2012-06-14 21:42 ` Chris Tapp @ 2012-06-15 6:01 ` Tomas Frydrych 2012-06-15 20:09 ` Chris Tapp 0 siblings, 1 reply; 5+ messages in thread From: Tomas Frydrych @ 2012-06-15 6:01 UTC (permalink / raw) To: yocto 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed understanding do_rootfs error 2012-06-15 6:01 ` Tomas Frydrych @ 2012-06-15 20:09 ` Chris Tapp 2012-06-16 9:09 ` Tomas Frydrych 0 siblings, 1 reply; 5+ messages in thread From: Chris Tapp @ 2012-06-15 20:09 UTC (permalink / raw) To: Tomas Frydrych; +Cc: yocto On 15 Jun 2012, at 07:01, Tomas Frydrych wrote: > 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). No, it works just fine. I had somehow got two conflicting versions pulled in at the same time (sorted by hiding the one I didn't expect and seeing what complained when I tried to build). Performance isn't great, but using Xfbdev works as fast (by 'eye') as it does on the unaccelerated hardware that the build was originally designed for. I've no plans to rewrite to use GLES (at this time) as the development version uses SDL with DirectFB (which is supposed to be getting ported to the RPi). The SDL version already works acceptably without DirectFB. > Incidentally, the GLES libs are not currently packaged by > meta-raspberrypi, I submitted a pull request for this yesterday. Thanks, that will be nice. I want to look at GLES for other things. May even update what I already have if it shows significant performance advantages (which it should). Looks like DirectFB has some sort of GLES support, so I also need to look at that. >> 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. It gets pulled in because that's what I've asked for in my image ;-) I did have a preferred provider, but, as I said above, I found an error that meant it wasn't working as expected. Chris Tapp opensource@keylevel.com www.keylevel.com ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Help needed understanding do_rootfs error 2012-06-15 20:09 ` Chris Tapp @ 2012-06-16 9:09 ` Tomas Frydrych 0 siblings, 0 replies; 5+ messages in thread From: Tomas Frydrych @ 2012-06-16 9:09 UTC (permalink / raw) To: yocto Hi Chris, On 15/06/12 21:09, Chris Tapp wrote: > On 15 Jun 2012, at 07:01, Tomas Frydrych wrote: >> Incidentally, the GLES libs are not currently packaged by >> meta-raspberrypi, I submitted a pull request for this yesterday. > > Thanks, that will be nice. I want to look at GLES for other things. > May even update what I already have if it shows significant > performance advantages (which it should). Looks like DirectFB has > some sort of GLES support, so I also need to look at that. I am aiming to get Clutter working on the RPI, but it looks like bits of the graphics drivers needed by libEGL are missing :( I opened an issue for this in github (https://github.com/raspberrypi/firmware/issues/43), we will see. Tomas ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-06-16 9:09 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2012-06-15 20:09 ` Chris Tapp 2012-06-16 9:09 ` Tomas Frydrych
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.