[yocto] Build failure (Segmentation fault) with Fido on CentOS

Hello, After several years away from OpenEmbedded and MVL6 I am back trying to work with Yocto and BitBake! My build system is a Core-i7 3770 running CentOS 6.7 (x86_64) with all the latest updates applied. I have cloned Fido from the git repository and set the target as "genericx86" and started

[yocto] Dumping sysvinit

Hello, Bit of a newbie question (probably) but what is the easiest way to dump sysvinit and use Busybox init in a core-image-minimal image? Thanks, Andy. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Dumping sysvinit

Mark wrote... > > Bit of a newbie question (probably) but what is the easiest way to dump > > sysvinit and use Busybox init in a core-image-minimal image? > > It has been a while since I've done this. But unless things have changed > dramatically. You will need to define your own custom image.

Re: [yocto] Dumping sysvinit

Hello all, > > I think if you remove/comment-out the last of those 3 lines or install > > your host's SDL-devel package you'll solve this issue (?) > > > Yes, that's right. Either disable the graphical qemu support, or install > the host's sdl-devel package so it can build. On my CentOS 6.7 host

Re: [yocto] Dumping sysvinit

Ross wrote... > > Now to figure out why the tar.gz file for the root file system has grown > > from just under 3MiB to almost 15MiB! > > That would be systemd... it pulls in a lot of libraries that are fairly common > on complex systems but on a minimal image less so. Back to plan A then, tryin

Re: [yocto] Dumping sysvinit

Hi Mike, > > Back to plan A then, trying to figure out how to get Busybox init and > mdev as the defaults in the image. > > Create your own distro, here's an example that uses mdev: > > https://github.com/topic-embedded-products/meta- > topic/blob/master/conf/distro/tiny.conf Thanks for pointin

[yocto] psplash wierdness

I have spent all morning fine tuning psplash on a PXE booting system using an NFS mounted root file system (all built with Yocto 1.8 for the intel-core2-32 machine) and all is exactly as I need. When I boot the system using an initrd of the same file system the first output from the init process i

Re: [yocto] psplash wierdness

Khem wrote... > Your initrd is missing /dev/null device it seems. You need to create it dring > build or > some runtime mechanism Hmmm, on further inspection it appears that in the /etc/rcS.d run level that psplash has been created as S00 while udev which is presumably going to create these

[yocto] Setting root password

Hello, Looking around the web and reading the assorted documents it seems to be that the defined way to set the root password is to remove "debug-tweaks" from EXTRA_IMAGE_FEATURES and to add the following lines to local.conf: require conf/distro/include/security_flags.inc INHERIT += "extrausers"

Re: [yocto] Setting root password

Hi Daniel, > I didn't know about this EXTRA_USERS_PARAMS. What I do is adding this > function to > my image. > # This function sets the password for root based on ROOT_PASSWD variable > set_root_password () { > local p=$(openssl passwd -1 -salt "My salt" "${ROOT_PASSWD}") >sed -e

Re: [yocto] Setting root password

Rudi wrote… > > Still, I think is a good ideia to understand what is going wrong with > > EXTRA_USERS_PARAMS, other users may having the same problem. > > EXTRA_USERS_PARAMS works for me all the time. The stanza is what I am using > in my image recipes: >  > EXTRA_USERS_PARAMS = "\ > groupadd dev

[yocto] TI DM355

Hello, I appreciate that the TI DM355 is now a very old device (ARM9 based) but I was wondering what the best starting point would be as I can't see it in the meta-ti layer. Any thoughts? Andy. -- ___ yocto mailing list yocto@yoctoproject.org https:/

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

Ross Burton wrote... >> it seems of limited value for YP to have a powerpc reference board, >> mpc8315e-rdb, that is essentially impossible to procure. is there any >> effort being made to look around for a newer powerpc reference board >> that people could actually buy? > >Do you have any suggest

Re: [yocto] any rumblings about a newer YP powerpc reference board than mpc8315e-rdb?

Robert wrote... > > I would look at one of the P10xx series QorIQ boards. Digi-Key list > > the P1021RDB-PC-ND and P1024RDB-PA-ND as being active parts which > > are either single or dual e500 cores. > > i would start with the machine definition files in the meta-fsl-ppc > layer: > > http://g

[yocto] wpewebkit, cog and libgles2

Hello, I am trying to add wpewebkit and the cog browser on top of a core-image-minimal build using Warrior. When I try to build bitbake gives me the following output: ERROR: Nothing PROVIDES 'virtual/egl' (but /home/me/yocto/sources/meta-webkit/recipes-browser/wpewebkit/wpewebkit_2.24.2.bb,

Re: [yocto] wpewebkit, cog and libgles2

Ross wrote... Well the libwpe build script says this: find_package(EGL REQUIRED) (https://github.com/WebPlatformForEmbedded/libwpe/blob/master/CMakeLists.txt) I’m confused now as there appears to be two active meta layers that support WPE WebKit. The one you reference meta-wpe and the one I

[yocto] Pre-installing node.js packages

Hello, Is there a way to add node.js packages into a build? I’m trying to avoid having to include npm and compiler into my target image. -Andy. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] wpewebkit, cog and libgles2

Joshua wrote... I’m confused now as there appears to be two active meta layers that support WPE WebKit. The one you reference meta-wpe and the one I was originally using meta-webkit (https://github.com/Igalia/meta-webkit) as that was the one that included Cog. Is one preferred to the other?

Re: [yocto] wpewebkit, cog and libgles2

Ross wrote... Search that until you find the DISTRO_FEATURES= and see if it it contains opengl. It presumably doesn't, and above the assignment it will tell you what removed it (or the absence of something adding it). The conf/distro/poky-atmel.conf file in meta-atmel contains the following

[yocto] Atmel device tree overlays

Hello, The meta-atmel layer includes a BSP recipe called dt-overlay-at91[1] that pulls in a number of .dtso files for various peripheral devices that can be connected to their reference boards. I can’t figure out how to get the overlays into the FIT image that my board is booting from. For

Re: [yocto] wpewebkit, cog and libgles2

I wrote... The conf/distro/poky-atmel.conf file in meta-atmel contains the following line: DISTRO_FEATURES_remove ?= "opengl wayland x11 3g nfc pulseaudio” Switching back to the regular DISTRO = “poky” seems to have got it building again. Switching back to poky caused a whole host of other i

[yocto] Building for AM335x with meta-ti and meta-qt5

I am trying to build a Yocto (warrior) image for the AM335x using meta-ti and meta-qt5 that will render directly to the GPU. Initially this will be for the Beaglebone Black but then ultimately will be for a custom hardware platform. In broad outline, I think, the software stack needs to look

Re: [yocto] Building for AM335x with meta-ti and meta-qt5

I wrote about trying to compile the SGX kernel modules giving up with the following error: | *** Multiarch build: no | *** Primary arch:target_armel | *** Secondary arch: none | ../config/core.mk:513: $(KERNELDIR)/vmlinux does not exist. Kbuild may fail. | eurasiacon/build/lin

[yocto] Shared area conflict

Hello, When I try to bitbake core-image-minimal it is giving up with the following error: ERROR: mesa-gl-2_18.1.9-r0 do_packagedata: The recipe mesa-gl is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/me/Yocto

Re: [yocto] Shared area conflict

Khem wrote... there are two recipes building/installing same files. You have to avoid conflicts via either removing them from one recipe or not installing them I’ve fixed this issue by creating a .bbappend file in my custom meta-layer that tells mesa not to install these two packages. Only on

[yocto] libgroove recipe

Hello, Does anyone know if there is a recipe for librgoove[1] and supporting libraries? I have searched in the OpenEmbedded Layer Index and more widely on the web but can’t see anything but maybe someone knows a dark corner it may be hiding in. -Andy. 1 - https://github.com/andrewrk/libgro

[yocto] Init stops working on second boot cycle

I’ve got a strange issue and I don’t know whether it is a Yocto related issue, a kernel issue or something else completely… I have an image that is built with thud (2.6.2) using meta-atmel for the SAMA5D2-Xplained reference board. I deploy the resulting .wic file to an SD card and boot the re

[yocto] Building SDK for macOS

This may be a really dumb question but is it possible to generate an SDK from a Yocto build that will allow cross compilation of an application to be done on a machine running macOS? -Andy. -- ___ yocto mailing list yocto@yoctoproject.org https://li

Re: [yocto] Building SDK for macOS

Ross wrote... Did a little poking. The need to build a SDK tarball on an existing macOS could probably be removed by using one of the convenient tarballs from https://github.com/phracker/MacOSX-SDKs/releases. The SDK is 32-bit, which is going to be an issue on modern macOS systems. The laye

[yocto] Partitioning SD cards

Hello, I am working on a custom platform where U-Boot will be programmed into an SPI NOR flash device and the ext4 file systems will be in a removable microSD card. The Linux kernel itself will be stored in the /boot directory of the root file system. The customer wants the (16GB) microSD c

Re: [yocto] Partitioning SD cards

Maciej wrote... How do I stop the wic generation process including the FAT formatted “boot” partition? This depends on the wic (.wks) file you are using. I have been using the default one (sdimage-bootpart.wks)? What is the best strategy for partitioning / formatting / mounting the second pa

Re: [yocto] Partitioning SD cards

I wrote... I have created a “wic” directory in my custom layer and copied sdimage-bootpart.wks into it as sdimage-project.wks without making any changes but “wic list image” throws an error with the new .wks file: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 37: inval

[yocto] Optimising imx6 performance for HTML5 using Cog + WPE WebKit

Hello, Broadening this out to the Freescale and Yocto mailing lists to see if any one has any answers… We are using Cog and WPE Webkit on an i.MX6 Solo based board with a user interface that is based on HTML5, Javascript and CSS and are having some issues with fading and other canvas effects

Re: [yocto] [wpe-webkit] Optimising imx6 performance for HTML5 using Cog + WPE WebKit

Carlos wrote... We start the browser with the following command line: cog --enable-accelerated-2d-canvas=1 appui/index.html How the performance compares if you disable accelerated-2d-canvas? It gets worse or its the same? It is the same. I have been testing with http://fabricjs.com//anima