[yocto] libtool problem while crosscompiling

Hi, I'm working with a imx6qsabrelite board and a sato SDK filesystem. I've built a complete SDK with bitbake -c populate_sdk and installed it. I have to modify the gstreamer gst-plugins-base libraries. I've sourced the environment, untarred the original gst-plugins-base-0.10.36.tar.gz, applied

[yocto] [meta-fsl] libtool problem while crosscompiling

Sorry, I've fixed the subject of my previous mail prepending the correct keywords. This was the message: Hi, I'm working with a imx6qsabrelite board and a sato SDK filesystem. I've built a complete SDK with bitbake -c populate_sdk and installed it. I have to modify the gstreamer

[yocto] Porting a BSP from Dylan to Dora

Hello, We have a BSP which is based on Dylan version. To port this BSP to Dora version what will be the steps needed ? Please can someone detail on this. Thanks, B.Sathish Kumar ::DISCLAIMER::

Re: [yocto] Porting a BSP from Dylan to Dora

I believe there is a migration guide in the Yocto Project Reference Manual Adam On Thu, Mar 13, 2014 at 8:10 AM, Sathish Kumar Balasubramaniam -ERS, HCL Tech b-sathishku...@hcl.com wrote: Hello, We have a BSP which is based on Dylan version. To port this BSP to Dora version what will

[yocto] What is the best practice for customizing libraries included in yocto distribution?

Hi everyone, what should I do to customize and crosscompile a library already distributed with yocto? I see 2 possibilities: 1. Build and install a toolchain and sysrootfs on local host and untar the original library, apply yocto distributed patches and then cross compile == I'm having

[yocto] Beagleboard booting kernel in qemu, halts

Hello everyone, I'm trying to run beagleboard image in qemu. So I've built the kernel and rootfs via yocto. But! Yocto generates zImage so I did: MACHINE=beagleboard bitbake virtual/kernel mkimage -A arm -O linux -T kernel -C none -a 0x80008000 -e 0x80008000 -n Linux kernel -d ./zImage uImage

Re: [yocto] Beagleboard booting kernel in qemu, halts

On 13 March 2014 18:59, Mateusz Kaczanowski kaczanowski.mate...@gmail.com wrote: Hello everyone, I'm trying to run beagleboard image in qemu. So I've built the kernel and rootfs via yocto. But! Yocto generates zImage so I did: MACHINE=beagleboard bitbake virtual/kernel mkimage -A arm -O

Re: [yocto] Beagleboard booting kernel in qemu, halts

On 13 March 2014 20:32, Paul Barker p...@paulbarker.me.uk wrote: On 13 March 2014 18:59, Mateusz Kaczanowski kaczanowski.mate...@gmail.com wrote: Hello everyone, I'm trying to run beagleboard image in qemu. So I've built the kernel and rootfs via yocto. But! Yocto generates zImage so I did:

[yocto] [meta-selinux PATCH 1/1] policycoreutils: semanage

When modifying an selinux login record, seobject.py, may try to log a value, self.sename, which has been preset to None and this will fail. So, we set it to something useful. Signed-off-by: Joe Slater jsla...@windriver.com --- .../policycoreutils-semanage-edit-user.patch | 21

[yocto] [meta-selinux PATCH 0/1] policycoreutils (semanage)

Fix a failure to modify records if we want to change the seuser for a login user. Just a log issue. I incremented PR. I think we should either do that are get rid of it. Joe Slater (1): policycoreutils: semanage .../policycoreutils-semanage-edit-user.patch | 21

Re: [linux-yocto] [PATCH v2 1/2] meta: update efi config fragment to include EFI_STUB by default

On 2014-03-13, 10:50 AM, Stefan Stanacar wrote: A number of bsps (intel-common, fri2, minnow) include the efi config. Some boot loaders (such as gummiboot, recently added to OE-core) require the kernel to be built with CONFIG_EFI_STUB. I think it would be useful to have that enabled by default