Re: [yocto] Can't find guile-2.0

2013-03-21 Thread Paul D. DeRocco
Still no joy. Nuked tmp/, re-checkedout the current danny branch head on both meta-openembedded and openembedded-core, and got the same error. Here are some things I notice about what's in my directory trees: My build tree shows both guile-1.8.7 and guile-2.0.6 in downloads. It shows stuff

[yocto] custom hddimg failure (mkdosfs: seek failed)

2013-03-21 Thread Insop Song
NATIVELSBSTRING = Ubuntu-12.10 TARGET_SYS= i586-poky-linux MACHINE = fri2 DISTRO= poky DISTRO_VERSION= 1.3+snapshot-20130321 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:9ffee9add2d0380f4025e7a678a166f25a7d659e meta

[yocto] Possible Cedartrail PVR build race

2013-03-21 Thread Chris Tapp
I think I have a build race condition for a project: 1) Using the meta-intel/cedartrail BSP; 2) Building under Danny 8.0; 3) Custom image; 4) Custom task; 5) OpenGLES application which runs under 'X'. If I do a clean build (i.e. after deleting tmp/ sstate-cache/) then my application produces

Re: [yocto] Possible Cedartrail PVR build race

2013-03-21 Thread Burton, Ross
On 21 March 2013 09:01, Chris Tapp opensou...@keylevel.com wrote: I think I have a build race condition for a project: 1) Using the meta-intel/cedartrail BSP; 2) Building under Danny 8.0; 3) Custom image; 4) Custom task; 5) OpenGLES application which runs under 'X'. If I do a clean build

Re: [yocto] Can't find guile-2.0

2013-03-21 Thread Burton, Ross
Hi Paul, On 21 March 2013 06:48, Paul D. DeRocco pdero...@ix.netcom.com wrote: In the metadata trees, meta-openembedded/meta-oe has recipes called guile_1.8.7.bb and guile-native_1.8.7.bb. poky-danny-8.0/meta and openembedded-core/meta both have recipes called guile_2.0.6.bb. The latter has

[yocto] Java on target machine

2013-03-21 Thread Florin Cristian Dan
First of all hello every body, A few days ago, i sent an e-mail in wich i was asking how can i run java apps on my target machine, mr. Paul Eggleton was kind enough to answar and gave me some links for enableing the layer, download the desired layer from LayerIndex and so on. I followed those

Re: [yocto] Building uio-pci-generic into core-image-minimal

2013-03-21 Thread Paul Eggleton
On Tuesday 19 March 2013 23:35:57 David Mulder wrote: From: Paul Eggleton [mailto:paul.eggle...@linux.intel.com] Sent: Thursday, February 21, 2013 11:53 AM I've now simply cherry-picked the two patches that came before this plus my patch from master on top of the 1.3 release tag, and

Re: [yocto] systemd timeouts started daemons

2013-03-21 Thread Burton, Ross
On 20 March 2013 08:27, Jukka Rissanen jukka.rissa...@linux.intel.com wrote: The reason for this was that systemd did not receive NameOwnerChanged dbus signal telling that the daemon managed to register its name to the system bus. I checked with dbus-monitor that these NameOwnerChanged

Re: [yocto] systemd timeouts started daemons

2013-03-21 Thread Jukka Rissanen
Hi Ross, On 21.03.2013 14:36, Burton, Ross wrote: On 20 March 2013 08:27, Jukka Rissanen jukka.rissa...@linux.intel.com wrote: The reason for this was that systemd did not receive NameOwnerChanged dbus signal telling that the daemon managed to register its name to the system bus. I checked

Re: [yocto] Autobuilder migration status.

2013-03-21 Thread Trevor Woerner
The new autobuilder looks great! One thing that's nice is how easy it is to look at the build and figure out from what commit the build is based. Clicking around in some of those builds, though, I can't seem to figure out what the various configurations are. For example: meta-fsl-arm has a number

[yocto] Problem in inserting kernel modules at Start up

2013-03-21 Thread Navani Srivastava
Hi, I am using poky -8.0 (danny) . I wish to insert kernel modules at start up. Before with denzil version I was adding kernel-modules to “IMAGE_INSTALL “ in rootfs image and it used to work like a charm. Now if I am doing the same it is giving me error as mentioned below. “error: Failed

Re: [yocto] Autobuilder migration status.

2013-03-21 Thread Eric Bénard
Hi Trevor, Le Thu, 21 Mar 2013 09:54:11 -0400, Trevor Woerner twoer...@gmail.com a écrit : The new autobuilder looks great! One thing that's nice is how easy it is to look at the build and figure out from what commit the build is based. Clicking around in some of those builds, though, I

Re: [yocto] systemd timeouts started daemons

2013-03-21 Thread Martin Jansa
Does this resolve also update-rc.d postinst trying to start /etc/init.d/dbus-1 and failing to find it? On Thu, Mar 21, 2013 at 1:36 PM, Burton, Ross ross.bur...@intel.com wrote: On 20 March 2013 08:27, Jukka Rissanen jukka.rissa...@linux.intel.com wrote: The reason for this was that systemd

Re: [yocto] systemd timeouts started daemons

2013-03-21 Thread Burton, Ross
On 21 March 2013 14:10, Martin Jansa martin.ja...@gmail.com wrote: Does this resolve also update-rc.d postinst trying to start /etc/init.d/dbus-1 and failing to find it? That's something else to be fixed. Ross ___ yocto mailing list

Re: [yocto] Autobuilder migration status.

2013-03-21 Thread Trevor Woerner
On Thu, Mar 21, 2013 at 10:05 AM, Eric Bénard e...@eukrea.com wrote: in the build log http://autobuilder.yoctoproject.org:8011/builders/nightly-fsl-arm/builds/18/steps/Building%20Images/logs/stdio you can see it builds for imx53qsb : MACHINE = imx53qsb Thank you, now I see how to

[yocto] Creating tailored image without standard rootfs files

2013-03-21 Thread Peter Bergin
Hi, for my Yocto build I want to create two separate images as output because in my system I have two separate partitions. One partition containing the root file system and one partition containing configuration and application data. What I want is to create an image only containing data and

Re: [yocto] Autobuilder migration status.

2013-03-21 Thread Trevor Woerner
I have looked at the output from a couple builds (nightly-fsl-arm, nightly-fsl-ppc, nightly-mips) and had a couple questions. Running poky/oe-init-build-env will produce a build/conf/local.conf, but the nightly builder prefers to puts its configurations into build/conf/auto.conf. Obviously

Re: [yocto] custom hddimg failure (mkdosfs: seek failed)

2013-03-21 Thread Khem Raj
+snapshot-20130321 TUNE_FEATURES = m32 core2 TARGET_FPU= meta meta-yocto meta-yocto-bsp= master:9ffee9add2d0380f4025e7a678a166f25a7d659e meta-intel meta-fri2 = master:7a5e19e0c7d5967ef7b003ab775b7210c0ee16d7 meta-realtime = image-sdk

Re: [yocto] Creating tailored image without standard rootfs files

2013-03-21 Thread Anders Darander
* Peter Bergin peter.ber...@qmatic.com [130321 16:10]: for my Yocto build I want to create two separate images as output because in my system I have two separate partitions. One partition containing the root file system and one partition containing configuration and application data. What I

Re: [yocto] Can't find guile-2.0

2013-03-21 Thread Paul D. DeRocco
From: Burton, Ross Ah ha! poky contains a copy of oe-core, so you don't need both, for a given version the meta/ directories will be identical (poky is the union of oe-core, bitbake, and meta-yocto). I'd forgotten that meta-oe used to have guile in. Presumably the problem here is that

Re: [yocto] Possible Cedartrail PVR build race

2013-03-21 Thread Chris Tapp
Hi Ross, On 21 Mar 2013, at 09:09, Burton, Ross wrote: On 21 March 2013 09:01, Chris Tapp opensou...@keylevel.com wrote: I think I have a build race condition for a project: 1) Using the meta-intel/cedartrail BSP; 2) Building under Danny 8.0; 3) Custom image; 4) Custom task; 5) OpenGLES

Re: [yocto] Creating tailored image without standard rootfs files

2013-03-21 Thread Tomas Frydrych
On 21/03/13 15:09, Peter Bergin wrote: for my Yocto build I want to create two separate images as output because in my system I have two separate partitions. One partition containing the root file system and one partition containing configuration and application data. What I want is to create

Re: [yocto] Can't find guile-2.0

2013-03-21 Thread Paul D. DeRocco
Actually, I did need the BBMASK so the problem was real. But I didn't need to include the openembedded-core/meta layer. Thanks so much for your help. Now to go on to find the next set of problems... -- Ciao, Paul D. DeRocco Paulmailto:pdero...@ix.netcom.com

[yocto] No keyboard in X

2013-03-21 Thread Chris Tapp
I've got a system (Danny, meta-intel-cedartrail) with a custom /etc/mini_x/session file which is used to run an application at startup. This all works to the extent that the application starts and runs, but the keyboard doesn't work - 'Esc' should cause the application to terminate and the X

[yocto] [meta-baryon] [PATCH v2 0/6] Updates and fixes

2013-03-21 Thread Kevin Strasser
Hi Paul, The old configuration bits are now included with the new samba recipe and everything is again working out-of-the-box. Also, I've added a commit to the series that removes our workaround for the NFS regression; it has been fixed both in OE-core as well as upstream. The following changes

Re: [yocto] No keyboard in X

2013-03-21 Thread Tomas Frydrych
On 21/03/13 20:11, Chris Tapp wrote: I've got a system (Danny, meta-intel-cedartrail) with a custom /etc/mini_x/session file which is used to run an application at startup. This all works to the extent that the application starts and runs, but the keyboard doesn't work - 'Esc' should cause

Re: [yocto] No keyboard in X

2013-03-21 Thread Chris Tapp
On 21 Mar 2013, at 20:38, Tomas Frydrych wrote: On 21/03/13 20:11, Chris Tapp wrote: I've got a system (Danny, meta-intel-cedartrail) with a custom /etc/mini_x/session file which is used to run an application at startup. This all works to the extent that the application starts and runs,

Re: [yocto] Possible Cedartrail PVR build race

2013-03-21 Thread Chris Tapp
On 21 Mar 2013, at 19:22, Chris Tapp wrote: Hi Ross, On 21 Mar 2013, at 09:09, Burton, Ross wrote: On 21 March 2013 09:01, Chris Tapp opensou...@keylevel.com wrote: I think I have a build race condition for a project: 1) Using the meta-intel/cedartrail BSP; 2) Building under Danny

[linux-yocto] [PATCH 1/2] Revert perf: temporary gcc 4.7 build fixes

2013-03-21 Thread tom . zanussi
From: Tom Zanussi tom.zanu...@linux.intel.com This has been fixed upstream, real fix to follow. This reverts commit 100ba7b476d4b595e8c6b7eca52a32bbbfe29cb1. Signed-off-by: Tom Zanussi tom.zanu...@intel.com --- tools/lib/traceevent/Makefile | 2 +- tools/perf/Makefile | 2 -- 2 files

[linux-yocto] [PATCH 2/2] libtraceevent: Remove hard coded include to /usr/local/include in Makefile

2013-03-21 Thread tom . zanussi
From: Jack Mitchell jack.mitch...@dbbroadcast.co.uk having /usr/local/include hardcoded into the makefile is not necessary as this is automatically included by GCC. It also infects cross-compile builds with the host systems includes. Signed-off-by: Jack Mitchell Acked-by: Namhyung Kim Cc: Ingo