yocto@lists.yoctoproject.org

Re: udev-hwdb - post installation error (PPC target)

On 11/27/2014 05:48 PM, Gaurang Shastri wrote: I think this correct. Please send out patch to openembedded-core@.... Regards, Chen Qi

By Chen Qi · #22349 ·

udev-hwdb - post installation error (PPC target)

Hi I have added systemd as my DISTRO_FEATURES for one of my ppc target. But in my log.do_rootfs, I can see that for "udev-hwdb" RPM, generated from "systemd", post-installation script failed with core

By Gaurang Shastri · #22348 ·

Install Java on Core-Image-Sato-Sdk

Hi, i tried to install Java (meta-oracle-java) on Core-image-Sato-sdk, but i always received this following error. Please help me ERROR: runstrip: ''i586-poky-linux-strip' --remove-section=.comment

By Tran TriTin <tritini@...> · #22347 ·

Creating a recipe to create /usr/local

Hi all, I'm not sure if emailing this is the most appropriate way and I apologize in advance if that's not. I have some scripts that require /usr/local to exist in Yocto and therefore I need to a

By Chan Kit Yu <yuchankit@...> · #22358 ·

[PATCH 2/2] yocto-bsp: Add mips64 support

mips64 support was recently added to the core BSPs; we should also support it in yocto-bsp. [YOCTO #5314] Signed-off-by: Tom Zanussi <tom.zanussi@...> --- scripts/lib/bsp/help.py

By Tom Zanussi · #22346 ·

[PATCH 1/2] yocto-bsp: Update templates to 3.17 kernel

Add 3.17 kernel support. Signed-off-by: Tom Zanussi <tom.zanussi@...> --- .../target/arch/arm/conf/machine/{{=machine}}.conf | 24 ++++------

By Tom Zanussi · #22345 ·

[PATCH 0/2] yocto-bsp 3.17 updates

This is the yocto-bsp 3.17 update, along with new mips64 support addressing [YOCTO #5314]. This is currently gated on the qemu and yocto-bsp machines moving to 3.17, which is in turn still currently

By Tom Zanussi · #22344 ·

Re: Headers missing in generated SDK

Syed, Your problem sounds similar to a problem I had getting my own headers and static library included in the SDK. Check out this thread to see if it helps.

By Matthew Z Schuckmann · #22343 ·

Re: Support for writable files with a read-only root file system

By Matthew Z Schuckmann · #22341 ·

Re: Support for writable files with a read-only root file system

Hi Mike, It sounds like using volatiles is the opposite of what you want. Unless I miss the point, what you want is to have your root file system mounted read-only with only select files

By Jim Rafert <jimr@...> · #22340 ·

Re: Automake error when building core-image-sato

Looking at those instructions, I think that any recent version should work. If you have problems, I'd suggest asking on the meta-ti mailing list meta-ti@... n.b. please keep the

By Gary Thomas · #22339 ·

Re: Automake error when building core-image-sato

Some information about your build environment will help, in particular what is your build host? Also, you might try a newer version of Poky/Yocto. --

By Gary Thomas · #22338 ·

Automake error when building core-image-sato

Hello, I am new to Yocto and trying to build an Image for Pandaboard using this guy's guidelines : http://maniacbug.wordpress.com/2012/08/03/pandayocto/ and encountered the following error when

By Daniel Pavel · #22337 ·

Re: Support for writable files with a read-only root file system

The one-size-fits-all solution is to use an unionfs, and a writable part in RAM or mounted elsewhere, e.g. in flash (typically a tiny jffs2 partition). It requires quite some scripting to get

By Mike Looijmans · #22336 ·

dizzy 1.7 udev automount misbehaviour

I have built an image using yocto dizzy 1.7 running on beaglebone using systemd as init system and I noticed a misbehaviour while inserting different removable storage device (sd cards /usb sticsk)

By Ayoub Zaki · #22335 ·

dizzy 1.7 udev automount misbehaviour

I have built an image using yocto dizzy 1.7 running on beaglebone using systemd as init system and I noticed a misbehaviour while inserting different removable storage device (sd cards /usb sticsk)

By Ayoub Zaki · #22342 ·

Re: New error in 1.7

Well, you could - but a better alternative would be to debug the issue. Where would gstg1allocator.h be expected to be found? Googling for that file only turns up your post, which is not a good sign

By Paul Eggleton · #22334 ·

Support for writable files with a read-only root file system

I've been investigating the support for read only root file systems and trying to suss out how to support persistent writeable files in my image where the root file system is read only, this seems

By Matthew Z Schuckmann · #22333 ·

Re: how to separate packages in downloads folder into those that run on target and those that do not run on target?

Dear Gangadhar, In message <CAKxnL=hSs5NNCQY9ZTZi0XWXGJOOn0i_0f-X7k7JksCZZrGo9w@...> you wrote: Do you think such a separation is possible at all? Depending on your target configuration,

By Wolfgang Denk <wd@...> · #22332 ·

how to separate packages in downloads folder into those that run on target and those that do not run on target?

Hi All, I want to separate the packages in downloads folder. I want to separate the packages into those that run on target and those that do not run on the target. The idea is to feed the

By Gangadhar N <gangadhar.ubuntu@...> · #22331 ·

Messages