[yocto] Adding Gnome to X11

Q. Gouès qgoues at actia-pcs.fr
Fri Mar 2 02:29:30 PST 2018


Actually the problem didn't come from doing IMAGE_INSTALL +=.

The problem came from the fact that in my recipe, I was adding the 
"IMAGE_INSTALL +=" line before the "inherit core-image" in which 
IMAGE_INSTALL is defined as a ?=. By doing that, the packages defined in 
the core-image class are not added because the variable IMAGE_INSTALL 
already exists.

Adding the "IMAGE_INSTALL +=" line after "inherit core-image" solved the 
problem.

I decided to use xfce as GUI because a recipe for the whole package 
exists (packagegroup-xfce-base).

Thanks for your help

*Quentin Gouès*
Ingénieur Développement Logiciel

*ACTIA* PCs
14, rue Charles Martigny
94700 MAISONS ALFORT (FRANCE)
Tel. +33 (0)1 42 07 18 00 - Fax +33 (0)1 42 07 85 55
http://www.actia-pcs.fr <http://www.actia-pcs.fr/>

Le 28/02/2018 à 17:17, Burton, Ross a écrit :
> Because by doing IMAGE_INSTALL += you wiped out the default value 
> which is a ?=.
>
> gnome-desktop3 isn't the GNOME interface though, it's just a small 
> library.
>
> If you want the full GNOME 3 desktop then you'll need to start with 
> meta-gnome and write more recipes, as it's not entirely packaged.
>
> Ross
>
> On 28 February 2018 at 14:10, Q. Gouès <qgoues at actia-pcs.fr 
> <mailto:qgoues at actia-pcs.fr>> wrote:
>
>     Hi,
>
>     I am trying to add gnome to my x11 image based on the recipe
>     core-image-x11. I am using Poky 2.0 (Jethro).
>
>     For that, I added the following line to my recipe:
>
>     /IMAGE_INSTALL += "gnome-desktop3"/
>
>     Unfortunately I get the following error:
>
>     /switch_root: can't execute '/sbin/init': No such file or directory//
>     //Kernel panic - not syncing: Attempted to kill init!
>     exitcode=0x00000100/
>
>     I tried the same thing with XFCE (I am trying to add a window
>     manager to my image) and I got the same results.
>
>     After taking a look at the rootfs in the iso file, I can notice
>     that the file '/sbin/init' is indeed missing. And it's not the
>     only file missing ! The rootfs went from ~420Mo to ~220Mo and the
>     list of files present in the rootfs went from:
>
>     /badblocks//
>     //blkid -> /bin/busybox.nosuid//
>     //bootlogd//
>     //debugfs//
>     //depmod -> /sbin/depmod.kmod//
>     //depmod.kmod -> ../bin/kmod//
>     //dumpe2fs//
>     //e2freefrag//
>     //e2fsck//
>     //e2image//
>     //e2undo//
>     //e4defrag//
>     //fdisk -> /bin/busybox.nosuid//
>     //filefrag//
>     //fsck -> /bin/busybox.nosuid//
>     //fsck.ext2//
>     //fsck.ext3//
>     //fsck.ext4//
>     //fsck.ext4dev//
>     //fstab-decode//
>     //fstrim -> /bin/busybox.nosuid//
>     //getty -> /bin/busybox.nosuid//
>     //halt -> /sbin/halt.sysvinit//
>     //halt.sysvinit//
>     //hdparm -> /sbin/hdparm.hdparm//
>     //hdparm.hdparm//
>     //hwclock -> /bin/busybox.nosuid//
>     //ifconfig -> /bin/busybox.nosuid//
>     //ifdown -> /bin/busybox.nosuid//
>     //ifup -> /bin/busybox.nosuid//
>     //init -> /sbin/init.sysvinit//
>     //init.sysvinit//
>     //insmod -> /sbin/insmod.kmod//
>     //insmod.kmod -> ../bin/kmod//
>     //ip -> /bin/busybox.nosuid//
>     //iwconfig//
>     //iwgetid -> iwconfig//
>     //iwlist -> iwconfig//
>     //iwpriv -> iwconfig//
>     //iwspy -> iwconfig//
>     //killall5//
>     //klogd -> /bin/busybox.nosuid//
>     //ldconfig//
>     //loadkmap -> /bin/busybox.nosuid//
>     //logread -> /bin/busybox.nosuid//
>     //logsave//
>     //losetup -> /bin/busybox.nosuid//
>     //lsmod -> /bin/lsmod.kmod//
>     //mke2fs//
>     //mkfs.ext2//
>     //mkfs.ext3//
>     //mkfs.ext4//
>     //mkfs.ext4dev//
>     //mklost+found//
>     //mkswap -> /bin/busybox.nosuid//
>     //modinfo -> /sbin/modinfo.kmod//
>     //modinfo.kmod -> ../bin/kmod//
>     //modprobe -> /sbin/modprobe.kmod//
>     //modprobe.kmod -> ../bin/kmod//
>     //nologin//
>     //pivot_root -> /bin/busybox.nosuid//
>     //populate-extfs.sh//
>     //poweroff -> /sbin/poweroff.sysvinit//
>     //poweroff.sysvinit -> halt.sysvinit//
>     //reboot -> /sbin/reboot.sysvinit//
>     //reboot.sysvinit -> halt.sysvinit//
>     //rmmod -> /sbin/rmmod.kmod//
>     //rmmod.kmod -> ../bin/kmod//
>     //route -> /bin/busybox.nosuid//
>     //runlevel -> /sbin/runlevel.sysvinit//
>     //runlevel.sysvinit//
>     //setconsole -> /bin/busybox.nosuid//
>     //shutdown -> /sbin/shutdown.sysvinit//
>     //shutdown.sysvinit//
>     //start-stop-daemon -> /bin/busybox.nosuid//
>     //sulogin -> /sbin/sulogin.util-linux//
>     //sulogin.util-linux//
>     //swapoff -> /bin/busybox.nosuid//
>     //swapon -> /bin/busybox.nosuid//
>     //switch_root -> /bin/busybox.nosuid//
>     //sysctl -> /bin/busybox.nosuid//
>     //syslogd -> /bin/busybox.nosuid//
>     //telinit -> init//
>     //udhcpc -> /bin/busybox.nosuid//
>     //vigr -> /sbin/vigr.shadow//
>     //vigr.shadow -> vipw.shadow//
>     //vipw -> /sbin/vipw.shadow//
>     //vipw.shadow/
>
>     to:
>
>     /ldconfig//
>     //nologin//
>     //sulogin -> /sbin/sulogin.util-linux//
>     //sulogin.util-linux//
>     //vigr -> /sbin/vigr.shadow//
>     //vigr.shadow -> vipw.shadow//
>     //vipw -> /sbin/vipw.shadow//
>     //vipw.shadow/
>
>     It looks like busybox was removed as well as other packages.
>
>     Do you have any idea why all these packages have been removed ?
>
>     Thanks
>
>     Quentin
>
>
>
>     --
>     _______________________________________________
>     yocto mailing list
>     yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/yocto
>     <https://lists.yoctoproject.org/listinfo/yocto>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180302/ffbafdfa/attachment.html>


More information about the yocto mailing list