Ross, Looking at the bug, I am trying with the latest commits now. When it failed, I looked at the build area, and found that the xorg-xserver package was built fine. I think the issue happened in the with rootfs generation. I haven't found why it was not included in the rootfs. From the bug I thought the issue got resolved in the latest tree HEAD, so I am going to test the latest head on few BSPs, and will dig further if I encounter the issue again.
Nitin > -----Original Message----- > From: Burton, Ross [mailto:ross.bur...@intel.com] > Sent: Wednesday, September 12, 2012 1:43 PM > To: Kamble, Nitin A > Cc: Zanussi, Tom; Hart, Darren; yocto@yoctoproject.org > Subject: Re: [yocto] [PATCH 0/1] Fix X issue on crownbay > > On 12 September 2012 21:14, Kamble, Nitin A <nitin.a.kam...@intel.com> > wrote: > > FYI While testing on the fishriver platform, I also find that there is no X > > log, > and looking further found out that xorg executable is not on the image. I > think the same thing is also happening on crownbay. > > There have been transient reports of Xorg missing in the qemu images too -- > transient because the reporter said that the next day's autobuilt image had > the package installed again. Very odd. > > In the broken systems you say there is no Xorg binary. Can you confirm that > there is no xserver-xorg package too? Can you inspect the build and see if > this failed, or if there is some machine configuration disaster which means it > doesn't think it needs to install an xserver? > > Ross > > FWIW, my qemuarm image from earlier today works. _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
