Re: [yocto] mount.nfs missing

2014-04-29 Thread Jegan Chandru 
Hi,

Could you please try adding nfs-utils-client??

I see this in nfs-utils recipe,
{{{
FILES_${PN}-client = "${base_sbindir}/*mount.nfs* ${sbindir}/*statd \
}}}

-JC



On Tue, Apr 29, 2014 at 8:31 PM, Rich Wilson  wrote:

> I have a working target hardware, except that /sbin/mount.nfs
> is missing from my root fs. I was able to get nfs to work by
> manually copying mount.nfs (and brethren) from my development
> system to the SD card, but it would be nice to hot have to do this!
>
> In local.conf, I have added the following:
>
> MACHINE ?= "zedboard-zynq7"
> DISTRO_FEATURES_append = " nfs"
> CORE_IMAGE_EXTRA_INSTALL += " nfs-utils"
>
> and built using
>
> rw@linux-cyy8:~/Downloads/poky-dora-10.0.1/build> bitbake core-image-basic
> Loading cache: 100%
> |#|
> ETA:  00:00:00
> Loaded 1194 entries from dependency cache.
> Parsing recipes: 100%
> |###|
> Time: 00:00:00
> Parsing of 862 .bb files complete (861 cached, 1 parsed). 1194 targets, 54
> skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
>
> Build Configuration:
> BB_VERSION= "1.20.0"
> BUILD_SYS = "x86_64-linux"
> NATIVELSBSTRING   = "openSUSE-project-12.3"
> TARGET_SYS= "arm-poky-linux-gnueabi"
> MACHINE   = "zedboard-zynq7"
> DISTRO= "poky"
> DISTRO_VERSION= "1.5.1"
> TUNE_FEATURES = " armv7a vfp neon zynq"
> TARGET_FPU= "vfp-neon"
> meta
> meta-yocto
> meta-yocto-bsp= ":"
> meta-xilinx   = "dora:aa7d677515ab7d45bbd3bdd6c5383f4143147c6d"
>
> NOTE: Preparing runqueue
> 
>
> mount.nfs is missing from the output:
>
> rw@linux-cyy8:~/Downloads/poky-dora-10.0.1/build/tmp/deploy/images/zedboard-zynq7>
> tar -tzf core-image-minimal-zedboard-zynq7.tar.gz | grep nfs
> ./etc/init.d/nfsserver
> ./etc/init.d/umountnfs.sh
> ./etc/init.d/mountnfs.sh
> ./etc/rc0.d/K20nfsserver
> ./etc/rc0.d/S31umountnfs.sh
> ./etc/nfs-utils.conf
> ./etc/rc5.d/S20nfsserver
> ./etc/rc2.d/S20nfsserver
> ./etc/rc4.d/S20nfsserver
> ./etc/rc6.d/K20nfsserver
> ./etc/rc6.d/S31umountnfs.sh
> ./etc/network/if-pre-up.d/nfsroot
> ./etc/rcS.d/S45mountnfs.sh
> ./etc/rc1.d/K20nfsserver
> ./etc/rc3.d/S20nfsserver
> ./usr/sbin/rpc.nfsd
> ./usr/sbin/nfsstat
> ./usr/lib/libnfsidmap.so.0.3.0
> ./usr/lib/libnfsidmap.so.0
> ./usr/lib/libnfsidmap/
> ./usr/lib/libnfsidmap/static.so
> ./usr/lib/libnfsidmap/nsswitch.so
> ./var/lib/nfs/
> ./var/lib/nfs/rmtab
> ./var/lib/nfs/sm/
> ./var/lib/nfs/xtab
> ./var/lib/nfs/etab
> ./var/lib/nfs/state
> ./var/lib/nfs/v4recovery/
> ./var/lib/nfs/statd/
> ./var/lib/nfs/sm.bak/
> rw@linux-cyy8
> :~/Downloads/poky-dora-10.0.1/build/tmp/deploy/images/zedboard-zynq7>
>
> I get the same result if I try core-image-basic.
>
> --
> Rich Wilson
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
JCP
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can one lay hands on a galileo-based dev kit?

2014-04-29 Thread Trevor Woerner 
PS. adafruit's website says they currently have them in stock:
http://www.adafruit.com/products/1637
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can one lay hands on a galileo-based dev kit?

2014-04-29 Thread Trevor Woerner 
On 29 April 2014 12:50, Robert P. J. Day  wrote:
> now if
> anyone in canada wants to weigh in and point me at the best source for
> one of these things, that would be great.

Hi Robert,

I found this company in B.C. via amazon.ca which appears to have some in stock:
http://www.canakit.com/arduino-intel-galileo.html

Hope this helps.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Adding qtwebkit fails do_rootfs in qt5

2014-04-29 Thread Manimehalai S 

Hi,

I have added meta-qt5 layer to my project and the filesystem settings are as 
below:

IMAGE_INSTALL_append += " arm-benchmarks icu qtbase qtbase-tools qtbase-plugins 
qtbase-fonts qtbase-plugins qtwebkit cinematicexperience gstreamer  
qtdeclarative oprofile ethtool libstdc++ alsa-lib alsa-utils alsa-tools 
alsa-conf alsa-conf-base bluez4 bluez-hcidump iproute2 busybox devmem2 
dosfstools gdb gdbserver i2c-tools initscripts iperf makedevs 
modutils-initscripts mtd-utils netbase udev-utils tslib-conf tslib-tests 
tslib-calibrate tinylogin"

When qtwebkit is added in the filesystem, build error occurs as below:

Log data follows:
| DEBUG: Executing shell function do_rootfs
| Note: configuring RPM platform settings
| Note: configuring RPM system provides
| Note: configuring RPM DB settings
| Note: configuring Smart settings
|
|
|
|
|
|
| Note: adding Smart channel xxx (80)
|
|
| Note: adding Smart channel armv7a_vfp_neon (75)
|
|
| Note: adding Smart channel all (10)
|
|
| Note: configuring RPM cross-install scriptlet_wrapper
|
| Updating cache...    
[100%]
|
| Saving cache...
|
| Error: qtwebkit not found in the base feeds (lec3517 armv7a-vfp-neon 
armv7a-vfp armv7a armv6-vfp armv6 armv5e-vfp armv5e armv5-vfp armv5 armv4 arm 
noarch any all).
| ERROR: Function failed: do_rootfs (see 
/home/manimehalais/dinesh/build/tmp/work/lec3517-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.25541
 for further information)
ERROR: Task 7 
(/home/manimehalais/dinesh/poky/meta/recipes-sato/images/core-image-sato.bb, 
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 6212 tasks of which 6210 didn't need to be rerun 
and 1 failed.
No currently running tasks (6211 of 6213)

Please help me to resolve the issue.

Thanks,
Manimehalai S

L&T Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.

L&T Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.

L&T Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
manimehalais@ashok-desktop:~/dinesh/build$ bitbake core-image-sato 
Parsing recipes: 100% |#| ETA:  00:00:00
Parsing of 1352 .bb files complete (0 cached, 1352 parsed). 1721 targets, 40 
skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
  
/home/manimehalais/dinesh/meta-qt5/recipes-devtools/cmake/cmake-native_2.8.12.2.bbappend
  
/home/manimehalais/dinesh/meta-qt5/recipes-devtools/cmake/cmake_2.8.12.2.bbappend

Build Configuration:
BB_VERSION= "1.18.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING   = "Ubuntu-12.04"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "lec3517"
DISTRO= "poky"
DISTRO_VERSION= "1.4.3"
TUNE_FEATURES = "armv7a vfp neon"
TARGET_FPU= "vfp-neon"
meta  
meta-yocto
meta-yocto-bsp= "dylan-9.0.3:6ef08331868c694ce7c3b31eeaac84e6aa8d660b"
meta-lec3517  = "master:8df5be2e602bcd707f07e5f49bdd0c8481c59e58"
toolchain-layer   = "dylan:cb182019c4f7485713cb50623240c01882448ffd"
meta-linaro-toolchain = "master:8df5be2e602bcd707f07e5f49bdd0c8481c59e58"
meta-oe   = "dylan:cb182019c4f7485713cb50623240c01882448ffd"
meta-qt5  = "master:7a8f5fe098c4a553249710f6869c01bac888d398"
meta-ruby = "dylan:cb182019c4f7485713cb50623240c01882448ffd"

NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for eglibc (eglibc, 
external-linaro-toolchain)
NOTE: consider defining a PREFERRED_PROVIDER entry to match eglibc
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
NOTE: multiple providers are available for jpeg-native (jpeg-native, 
libjpeg-turbo-native)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native
NOTE: Preparing runqueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: Function failed: do_rootfs (see 
/home/manimehalais/dinesh/build/tmp/work/lec3517-poky-linux-gnueabi/core-image-sato/1.0-r0/temp/log.do_rootfs.25541
 for further information)
ERROR: Logfile of failure stored in: 
/home/manimehalais/dinesh/build/tmp/work/lec3517-poky-linux-gnuea

Re: [yocto] 1.5.2.rc3 now available for QA

2014-04-29 Thread Saul Wold 

On 04/28/2014 09:50 PM, Flanagan, Elizabeth wrote:

http://autobuilder.yoctoproject.org/pub/releases/yocto-1.5.2.rc3

bitbake 0a94e568152de550dedc8135a766beb18bf064ab
eclipse-poky-juno 79cd3c6ff119526f3f85567253450d2e857afed0
eclipse-poky-kepler e842d41f05066df1533a2788e650f0be213ad5b5
meta-fsl-arm 5fdb620c09df11e70434092f675c891e0ba84108
meta-fsl-ppc 40465bac88ca28b554cff35346341d19552548bf
meta-intel acf2b4013d981563081bc072e778c4caaab7c67d
meta-minnow 9aa60d0eaf03fe30670acf581eaf7e57c76b5f99
meta-qt3 4772424ab69908d4e3b9d6d4717ca889468e6acd
oecore 97bc1bce9a226cc02db8a5afc2c0d4f4f70034a6
poky 9b7d43963f54d25e087a4cc55623a4cfeac121a9




Dora is now officially updated to

b626e109e83384558f45dc2e30e7caec677ce1db

The build that was done was based on my branch with one patch, this is 
updated with that patch and a BA SRCREV Bump.


I am not sure if we need another full build out on the AB or not, or 
just a Build appliance build?


Sau!

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] fsl-image-multimedia-full build failure on master branch

2014-04-29 Thread Eric Nelson 

Hi Mahyar,

On 04/29/2014 12:39 PM, Mahyar Yaghmaee wrote:

Hello,

I can not build fsl-image-multimedia-full as "fsl_debug.h" seems not to
be present.
here's the error log:



This is the wrong forum for the question, and I suspect that
this has something to do with Lauren's recent patch set for
the upcoming Freescale release.

Regards,


Eric

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[linux-yocto] [PULL REQUEST] Kernel: 3.10 Branch: standard/axxia/base

2014-04-29 Thread Paul, Charlie 
Bruce,

Here is the  pull request for the second set of patches

Charlie

The following changes since commit a72435875d8a4b4e5d61779dd823c59fd4180921:

  gpio: repairs merge comflict (2014-04-22 14:44:24 -0700)

are available in the git repository at:

  g...@github.com:butlerpaul/lsikernel-3.10 sab-next-2

for you to fetch changes up to 4346baaae2fee096212957f62984aeca909ad4f8:

  ARM: axxia: Flush L3 in kexec_reinit (2014-04-28 16:24:18 -0700)


Anders Berg (9):
  i2c-axxia: Avoid timeout when interrupt delayed
  dma: lsi-dma32: Add parameter to setup burst size
  dma: lsi-dma32: Handle DMA transfer sizes > 1MB
  ARM: axxia: dts: Enable sp804 timers by default
  ARM: axxia: Cleanup timer init code
  i2c: axxia: Add support for 10-bit addressing
  ARM: axxia: Alloc GIC to be initialized from non-primary core
  ARM: axxia: Fix release of CPUs with booted via kexec
  ARM: axxia: Flush L3 in kexec_reinit

David Mercado (2):
  LSI AXM55xx: Fix PMU handler issue
  LSI AXM55xx: Fix CPU hotplug

John Jacques (4):
  arch/powerpc: Disable the ACP NAND Driver for 3500
  arch/powerpc: Fix Compile Error when the Target is PowerPC
  axxia: Use the Device Tree for MDIO Clock Offset/Period if Provided
  arch/powerpc: Support Older Machine Name for LSI Axxia

arch/arm/boot/dts/axm5504-emu.dts|2 +
arch/arm/boot/dts/axm5507-emu.dts|2 +
arch/arm/boot/dts/axm5516-amarillo.dts   |2 +
arch/arm/boot/dts/axm55xx.dtsi   |1 -
arch/arm/mach-axxia/axxia-gic.c  |   47 +--
arch/arm/mach-axxia/axxia.c  |  102 +++---
arch/arm/mach-axxia/axxia.h  |1 +
arch/arm/mach-axxia/hotplug.c|2 +-
arch/arm/mach-axxia/include/mach/axxia-gic.h |1 -
arch/arm/mach-axxia/platsmp.c|   27 ++--
arch/powerpc/boot/dts/acp25xx.dts|3 +
arch/powerpc/boot/dts/acp342x.dts|3 +
arch/powerpc/boot/dts/acp344x.dts|3 +
arch/powerpc/boot/dts/acp35xx.dts|3 +
arch/powerpc/platforms/44x/acpx1.c   |5 +-
drivers/dma/lsi-dma32.c  |  185 +++---
drivers/dma/lsi-dma32.h  |4 +-
drivers/i2c/busses/i2c-axxia.c   |   84 +++-
drivers/mtd/nand/lsi_acp_nand.c  |7 +
drivers/net/ethernet/lsi/lsi_acp_mdio.c  |   33 +++--
20 files changed, 306 insertions(+), 211 deletions(-)
-- 
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto

[yocto] fsl-image-multimedia-full build failure on master branch

2014-04-29 Thread Mahyar Yaghmaee 
Hello,

I can not build fsl-image-multimedia-full as "fsl_debug.h" seems not to be
present.
here's the error log:


|
/home/mahyar/yocto/y02/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.10-r0/gst-fsl-plugins-3.0.10/libs/vss/mfw_gst_vss_common.c:52:23:
fatal error: fsl_debug.h: No such file or directory
|  #include "fsl_debug.h"
|^
| compilation terminated.
|
/home/mahyar/yocto/y02/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.10-r0/gst-fsl-plugins-3.0.10/libs/vss/mfw_gst_video_surface.c:57:23:
fatal error: fsl_debug.h: No such file or directory
|  #include "fsl_debug.h"
|^
| compilation terminated.
| make[1]: *** [libgstfsl_0.10_la-mfw_gst_video_surface.lo] Error 1
| make[1]: *** Waiting for unfinished jobs
| make[1]: *** [libgstfsl_0.10_la-mfw_gst_vss_common.lo] Error 1
| make[1]: Leaving directory
`/home/mahyar/yocto/y02/build/tmp/work/nitrogen6x-poky-linux-gnueabi/gst-fsl-plugin/3.0.10-r0/build/libs'
| make: *** [all-recursive] Error 1
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.



Any idea what's the problem here?

Regards,
Mahyar
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can one lay hands on a galileo-based dev kit?

2014-04-29 Thread Robert P. J. Day 
On Tue, 29 Apr 2014, Alex J Lennon wrote:

>
> On 29/04/2014 17:34, Robert P. J. Day wrote:
> >   i've just been asked to design a linux device drivers course based
> > on the arduino-compatible intel galileo processor, so my first TODO
> > item is to lay hands on a galileo-based dev kit, for which this looks
> > like the obvious choice:
> >
> > https://software.intel.com/en-us/iotdevkit
> >
> > but that page says "upcoming". does it exist? my normal go-to source
> > up here, digikey.ca, shows zero in stock. where can i lay hands on
> > one (if possible)? thanks.
>
> If it helps I had a Galileo Dev Kit delivered from RS (UK) a couple of
> days ago.
>
> http://uk.rs-online.com/web/p/processor-microcontroller-development-kits/7919611/

  ok, so that tells me it's at least available, so i should be able to
track it down online around here somewhere. good to know. now if
anyone in canada wants to weigh in and point me at the best source for
one of these things, that would be great.

  BTW, i notice that's the basic board, while this:

https://software.intel.com/en-us/iotdevkit

seems a bit more bundled. does anyone know if there is any significant
difference?

  as i mentioned earlier, a client wants a drivers course based on
this processor, so i'd also want the ability to possibly order a bunch
of them for the students as class time approaches (whenever that is).

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] can one lay hands on a galileo-based dev kit?

2014-04-29 Thread Alex J Lennon 

On 29/04/2014 17:34, Robert P. J. Day wrote:
>   i've just been asked to design a linux device drivers course based
> on the arduino-compatible intel galileo processor, so my first TODO
> item is to lay hands on a galileo-based dev kit, for which this looks
> like the obvious choice:
>
> https://software.intel.com/en-us/iotdevkit
>
> but that page says "upcoming". does it exist? my normal go-to source
> up here, digikey.ca, shows zero in stock. where can i lay hands on
> one (if possible)? thanks.

If it helps I had a Galileo Dev Kit delivered from RS (UK) a couple of
days ago.

http://uk.rs-online.com/web/p/processor-microcontroller-development-kits/7919611/

(I'm actually a bit confused about how the Galileo IoT collection of
meta-foo layers relates to the primary meta-foo
 sources, as I can't seem to find an independent meta-clanton ;ayer
which I guess I'd need. Early days yet, but am planning
 on working through this as soon as I get some time as I want to test a
build with meta-moo support on Galileo)

Cheers, Alex

> rday
>

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] can one lay hands on a galileo-based dev kit?

2014-04-29 Thread Robert P. J. Day 

  i've just been asked to design a linux device drivers course based
on the arduino-compatible intel galileo processor, so my first TODO
item is to lay hands on a galileo-based dev kit, for which this looks
like the obvious choice:

https://software.intel.com/en-us/iotdevkit

but that page says "upcoming". does it exist? my normal go-to source
up here, digikey.ca, shows zero in stock. where can i lay hands on
one (if possible)? thanks.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Antwort: Re: Antwort: Re: building qtbase for raspberry pi fails

2014-04-29 Thread Felix01 Fischer 
Including the headers didn't work, because the dependencies wouldn't be 
fullfilled.

I managed to get around the first error by manipulating the mkspecs and 
adding the full path of libGLESv2.so to it.

The next error is that "eglDestroyContext" is not defined.

Via "grep -r -i  'eglDestroyContext' ./" I'm able to find out, that 
libEGL_static.a libkhrn_static.a and libEGL.so have this string ( 
libEGL.so was the file which threw the errors in the first place, I don't 
know what is going on)

Adding one of these three files to the mkspecs results in  "not found" 
errors of them (but they are there, no typos, I triple-checked, full path 
specified)

My guess would be to look in the elf header for the dynamic part, I did 
this for libEGL.so, everything seems fine to me.

my head spins, knocking-off time!

Expect my next answer next tuesday due to holidays in germany :-)

Thank you for your help so far,

Felix



Vaduva alexandru  schrieb am 29.04.2014 
15:26:27:

> Von: Vaduva alexandru 
> An: Felix01 Fischer , 
> Kopie: "yocto@yoctoproject.org" 
> Datum: 29.04.2014 15:30
> Betreff: Re: Antwort: Re: [yocto] building qtbase for raspberry pi fails
> 
> You may try and  find the headers containing those undefined 
> functions and include them into rootfs, more exaclty into usr/
> include or similar.
> 
> On Tuesday, April 29, 2014 3:56 PM, Felix01 Fischer 
>  wrote:
> Unfortunately there is no library. After either "bitbake -c compile 
> userland" or "bitbake userland" there are the source files (*.h *.c)
> and one named "*.c.o" but no *.o file exists 
> 
> Vaduva alexandru  schrieb am 29.04.
> 2014 14:10:48:
> 
> > Von: Vaduva alexandru 
> 
> > An: Felix01 Fischer , 
> > "yocto@yoctoproject.org" , 
> > Datum: 29.04.2014 14:11 
> > Betreff: Re: [yocto] building qtbase for raspberry pi fails 
> > 
> > Did you tried copying the glxx library into the rootfs lib directory? 
> > 
> > On Tuesday, April 29, 2014 2:38 PM, Felix01 Fischer 
> >  wrote: 
> > I've been able to narrow my problem futher down:
> > 
> > the meta-raspberrypi layer contains a bb called "userland_git.bb" 
> > (meta-raspberrypi/recipes-graphics/userland/userland_git.bb). 
> > the source for this layer is github.com/raspberrypi/userland.git. I 
> > cloned this repository and searched for the undefined references.
> > 
> > This repository contains the source code for the ARM side libraries 
> > used on Raspberry Pi. These typically are installed in /opt/vc/lib 
> > and includes source for the ARM side code to interface to: EGL, 
> > mmal, GLESv2, vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 
> > 
> > I had success! All my undefined references are defined in userland/
> > interface/khronos/glxx/glxx_client.(h|c).
> > 
> > But still I haven't figured out how to get this build correctly so 
> > qtbase can find and use it. 
> > 
> > Any suggestions?
> > 
> > Felix
> > 
> > 
> > yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38: 
> > 
> > > Von: Felix01 Fischer  
> > 
> > > An: yocto@yoctoproject.org, 
> > > Datum: 25.04.2014 15:33 
> > > Betreff: [yocto] building qtbase for raspberry pi fails 
> > > Gesendet von: yocto-boun...@yoctoproject.org 
> > > 
> > > Hello everybody, 
> > > first, I hope I have choosen the right mailing list for my problem. 
> > > If not, please tell me.
> > > 
> > > I have problems getting Qt5 building and running on a raspberry pi 
> > > (512 Mb Version).
> > > I'm using today's master branch from yocto & meta-raspberrypi ( 
> > > git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5 
).
> > > Building without a change in qtbase doesn't work because the OpenGL 
> > > Test fails ( the raspberry pi only suppports GLESv2). 
> > > When building with a qtbase_X.Y.Z.bbappend and 
> > > "PACKAGECCONFIG_append = " gles2" in order to use eglfs the mess 
beginns.
> > > First, building qtbase fails because qtbase-opensource-src-5.2.1/
> > > config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> > > After including this manually in "meta-qt5/recipes-qt/qt5/
> > > qtbase.inc" by adding the last line to configure 
> > > do_configure() { 
> > > 
> > > [.] 
> > > 
> > > ${S}/configure -v \ 
> > > -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \ 
> > > 
> > > [.] 
> > > 
> > > } 
> > > 
> > > 
> > > the next error is the following: 
> > > | EGL auto-detection... () 
> > > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork -
> > > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > > build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> > > unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE  -
> > > I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++ -
> > > I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl -
> > > I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> > > vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> > > config.tests/qpa/egl/egl.cp

[yocto] mount.nfs missing

2014-04-29 Thread Rich Wilson 
I have a working target hardware, except that /sbin/mount.nfs
is missing from my root fs. I was able to get nfs to work by
manually copying mount.nfs (and brethren) from my development
system to the SD card, but it would be nice to hot have to do this!

In local.conf, I have added the following:

MACHINE ?= "zedboard-zynq7"
DISTRO_FEATURES_append = " nfs"
CORE_IMAGE_EXTRA_INSTALL += " nfs-utils"

and built using

rw@linux-cyy8:~/Downloads/poky-dora-10.0.1/build> bitbake core-image-basic
Loading cache: 100%
|#|
ETA:  00:00:00
Loaded 1194 entries from dependency cache.
Parsing recipes: 100%
|###|
Time: 00:00:00
Parsing of 862 .bb files complete (861 cached, 1 parsed). 1194 targets, 54
skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION= "1.20.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING   = "openSUSE-project-12.3"
TARGET_SYS= "arm-poky-linux-gnueabi"
MACHINE   = "zedboard-zynq7"
DISTRO= "poky"
DISTRO_VERSION= "1.5.1"
TUNE_FEATURES = " armv7a vfp neon zynq"
TARGET_FPU= "vfp-neon"
meta
meta-yocto
meta-yocto-bsp= ":"
meta-xilinx   = "dora:aa7d677515ab7d45bbd3bdd6c5383f4143147c6d"

NOTE: Preparing runqueue


mount.nfs is missing from the output:

rw@linux-cyy8:~/Downloads/poky-dora-10.0.1/build/tmp/deploy/images/zedboard-zynq7>
tar -tzf core-image-minimal-zedboard-zynq7.tar.gz | grep nfs
./etc/init.d/nfsserver
./etc/init.d/umountnfs.sh
./etc/init.d/mountnfs.sh
./etc/rc0.d/K20nfsserver
./etc/rc0.d/S31umountnfs.sh
./etc/nfs-utils.conf
./etc/rc5.d/S20nfsserver
./etc/rc2.d/S20nfsserver
./etc/rc4.d/S20nfsserver
./etc/rc6.d/K20nfsserver
./etc/rc6.d/S31umountnfs.sh
./etc/network/if-pre-up.d/nfsroot
./etc/rcS.d/S45mountnfs.sh
./etc/rc1.d/K20nfsserver
./etc/rc3.d/S20nfsserver
./usr/sbin/rpc.nfsd
./usr/sbin/nfsstat
./usr/lib/libnfsidmap.so.0.3.0
./usr/lib/libnfsidmap.so.0
./usr/lib/libnfsidmap/
./usr/lib/libnfsidmap/static.so
./usr/lib/libnfsidmap/nsswitch.so
./var/lib/nfs/
./var/lib/nfs/rmtab
./var/lib/nfs/sm/
./var/lib/nfs/xtab
./var/lib/nfs/etab
./var/lib/nfs/state
./var/lib/nfs/v4recovery/
./var/lib/nfs/statd/
./var/lib/nfs/sm.bak/
rw@linux-cyy8
:~/Downloads/poky-dora-10.0.1/build/tmp/deploy/images/zedboard-zynq7>

I get the same result if I try core-image-basic.

-- 
Rich Wilson
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing kernel, modules and dtb for beaglebone on core-image-minimal

2014-04-29 Thread Stefan Stanacar 
On Tue, Apr 29, 2014 at 5:35 PM, Diego Sueiro  wrote:
>
> Stefan,
>
> On Tue, Apr 29, 2014 at 11:32 AM, Stefan Stanacar  wrote:
>>
>> That's not a bug :), it's intended. The README.hardware clearly states that 
>> for deploying a core-image-minimal you need to unpack the modules and copy 
>> the dtbs over.
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README.hardware#n244
>>
>> There is a reason for that, mainly beacause the way core-image-minimal 
>> recipe works.
>>  A BSP usually adds kernel-modules and other stuff to MACHINE_EXTRA_RDEPENDS 
>> but not all images respect that (they need to inherit core-image.bbclass and 
>> not overwrite IMAGE_INSTALL).
>
>
> Thanks. Got it.
> Why I never RTFM or at least the README file?
>
>

No problem, you're welcome.

FWIW the beaglebone machine defintion does:

MACHINE_EXTRA_RRECOMMENDS = " kernel-modules kernel-devicetree"

which ultimately get pulled in packagegroup-base.

Cheers,
Stefan

>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing kernel, modules and dtb for beaglebone on core-image-minimal

2014-04-29 Thread Diego Sueiro 
Stefan,
On Tue, Apr 29, 2014 at 11:32 AM, Stefan Stanacar  wrote:

> That's not a bug :), it's intended. The README.hardware clearly states
> that for deploying a core-image-minimal you need to unpack the modules and
> copy the dtbs over.
>
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README.hardware#n244
>
> There is a reason for that, mainly beacause the way core-image-minimal
> recipe works.
>  A BSP usually adds kernel-modules and other stuff to
> MACHINE_EXTRA_RDEPENDS but not all images respect that (they need to
> inherit core-image.bbclass and not overwrite IMAGE_INSTALL).


Thanks. Got it.
Why I never RTFM or at least the README file?


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

/*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Missing kernel, modules and dtb for beaglebone on core-image-minimal

2014-04-29 Thread Stefan Stanacar 
That's not a bug :), it's intended. The README.hardware clearly states that
for deploying a core-image-minimal you need to unpack the modules and copy
the dtbs over.

http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/README.hardware#n244

There is a reason for that, mainly beacause the way core-image-minimal
recipe works.
 A BSP usually adds kernel-modules and other stuff to
MACHINE_EXTRA_RDEPENDS but not all images respect that (they need to
inherit core-image.bbclass and not overwrite IMAGE_INSTALL).

HTH,
Stefan


On Tue, Apr 29, 2014 at 5:17 PM, Diego Sueiro wrote:

> Folks,
>
> I'm using daisy branch of yocto and I realized that kernel and dtb files
> were not present on /boot and there were no modules installed on
> /lib/modules/3.14.0-yocto-standard.
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Missing kernel, modules and dtb for beaglebone on core-image-minimal

2014-04-29 Thread Diego Sueiro 
Folks,

I'm using daisy branch of yocto and I realized that kernel and dtb files
were not present on /boot and there were no modules installed on
/lib/modules/3.14.0-yocto-standard.



Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br

/*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Antwort: Re: building qtbase for raspberry pi fails

2014-04-29 Thread Vaduva alexandru 
Another solution is point the location of the necessary headers to the compiler 
or the necessary task.
I believe do_configure() one.


On , Vaduva alexandru  wrote:
 
You may try and  find the headers containing those undefined functions and 
include them into rootfs, more exaclty into usr/include or similar.


On Tuesday, April 29, 2014 3:56 PM, Felix01 Fischer  
wrote:
 
Unfortunately there is no library. After
either "bitbake -c compile userland" or "bitbake userland"
there are the source files (*.h *.c) and one named "*.c.o" but
no *.o file exists 

Vaduva alexandru 
schrieb am 29.04.2014 14:10:48:


> Von: Vaduva alexandru 

> An: Felix01 Fischer , 
> "yocto@yoctoproject.org" ,  
> Datum: 29.04.2014 14:11 
> Betreff: Re: [yocto] building qtbase for raspberry
pi fails 
> 
> Did you tried copying the glxx library into the rootfs lib directory? 
> 
> On Tuesday, April 29, 2014 2:38 PM, Felix01 Fischer 
>  wrote: 
> I've been able to narrow my problem futher down:
> 
> the meta-raspberrypi layer contains a bb called "userland_git.bb" 
> (meta-raspberrypi/recipes-graphics/userland/userland_git.bb). 
> the source for this layer is github.com/raspberrypi/userland.git.
I 
> cloned this repository and searched for the undefined references.
> 
> This repository contains the source code for the ARM side libraries 
> used on Raspberry Pi. These typically are installed in /opt/vc/lib 
> and includes source for the ARM side code to interface to: EGL, 
> mmal, GLESv2, vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 
> 
> I had success! All my undefined references are defined in userland/
> interface/khronos/glxx/glxx_client.(h|c).
> 
> But still I haven't figured out how to get this build correctly so 
> qtbase can find and use it. 
> 
> Any suggestions?
> 
> Felix
> 
> 
> yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38: 
> 
> > Von: Felix01 Fischer  
> 
> > An: yocto@yoctoproject.org, 
> > Datum: 25.04.2014 15:33 
> > Betreff: [yocto] building qtbase for raspberry pi fails 
> > Gesendet von: yocto-boun...@yoctoproject.org 
> > 
> > Hello everybody, 
> > first, I hope I have choosen the right mailing list for my problem. 
> > If not, please tell me.
> > 
> > I have problems getting Qt5 building and running on a raspberry
pi 
> > (512 Mb Version).
> > I'm using today's master branch from yocto & meta-raspberrypi
( 
> > git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5
).
> > Building without a change in qtbase doesn't work because the
OpenGL 
> > Test fails ( the raspberry pi only suppports GLESv2). 
> > When building with a qtbase_X.Y.Z.bbappend and 
> > "PACKAGECCONFIG_append = " gles2" in order to
use eglfs the mess beginns.
> > First, building qtbase fails because qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> > After including this manually in "meta-qt5/recipes-qt/qt5/
> > qtbase.inc" by adding the last line to configure 
> > do_configure() { 
> >   
> > [.] 
> > 
> >     ${S}/configure -v \ 
> > -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/
\ 
> > 
> > [.] 
> > 
> > } 
> > 
> >     
> > the next error is the following: 
> > | EGL auto-detection... () 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork
-
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> > unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE
 -
> > I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++
-
> > I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl
-
> > I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> > vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp: In function 'int main(int, char**)': 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp:46:12: warning: unused variable 'x' [-Wunused-variable] 
> > |      EGLint x = 0; 
> > |             ^ 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork
-
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--
> > as-needed -Wl,-O1 -o egl egl.o   -lEGL 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to 
> `glxx_client_GetRenderbufferParameteriv'
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl20_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl11_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glintAttribPointer' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroo

Re: [yocto] Antwort: Re: building qtbase for raspberry pi fails

2014-04-29 Thread Vaduva alexandru 
You may try and  find the headers containing those undefined functions and 
include them into rootfs, more exaclty into usr/include or similar.


On Tuesday, April 29, 2014 3:56 PM, Felix01 Fischer  
wrote:
 
Unfortunately there is no library. After
either "bitbake -c compile userland" or "bitbake userland"
there are the source files (*.h *.c) and one named "*.c.o" but
no *.o file exists 

Vaduva alexandru 
schrieb am 29.04.2014 14:10:48:


> Von: Vaduva alexandru 

> An: Felix01 Fischer , 
> "yocto@yoctoproject.org" ,  
> Datum: 29.04.2014 14:11 
> Betreff: Re: [yocto] building qtbase for raspberry
pi fails 
> 
> Did you tried copying the glxx library into the rootfs lib directory? 
> 
> On Tuesday, April 29, 2014 2:38 PM, Felix01 Fischer 
>  wrote: 
> I've been able to narrow my problem futher down:
> 
> the meta-raspberrypi layer contains a bb called "userland_git.bb" 
> (meta-raspberrypi/recipes-graphics/userland/userland_git.bb). 
> the source for this layer is github.com/raspberrypi/userland.git.
I 
> cloned this repository and searched for the undefined references.
> 
> This repository contains the source code for the ARM side libraries 
> used on Raspberry Pi. These typically are installed in /opt/vc/lib 
> and includes source for the ARM side code to interface to: EGL, 
> mmal, GLESv2, vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 
> 
> I had success! All my undefined references are defined in userland/
> interface/khronos/glxx/glxx_client.(h|c).
> 
> But still I haven't figured out how to get this build correctly so 
> qtbase can find and use it. 
> 
> Any suggestions?
> 
> Felix
> 
> 
> yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38: 
> 
> > Von: Felix01 Fischer  
> 
> > An: yocto@yoctoproject.org, 
> > Datum: 25.04.2014 15:33 
> > Betreff: [yocto] building qtbase for raspberry pi fails 
> > Gesendet von: yocto-boun...@yoctoproject.org 
> > 
> > Hello everybody, 
> > first, I hope I have choosen the right mailing list for my problem. 
> > If not, please tell me.
> > 
> > I have problems getting Qt5 building and running on a raspberry
pi 
> > (512 Mb Version).
> > I'm using today's master branch from yocto & meta-raspberrypi
( 
> > git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5
).
> > Building without a change in qtbase doesn't work because the
OpenGL 
> > Test fails ( the raspberry pi only suppports GLESv2). 
> > When building with a qtbase_X.Y.Z.bbappend and 
> > "PACKAGECCONFIG_append = " gles2" in order to
use eglfs the mess beginns.
> > First, building qtbase fails because qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> > After including this manually in "meta-qt5/recipes-qt/qt5/
> > qtbase.inc" by adding the last line to configure 
> > do_configure() { 
> >   
> > [.] 
> > 
> >     ${S}/configure -v \ 
> > -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/
\ 
> > 
> > [.] 
> > 
> > } 
> > 
> >     
> > the next error is the following: 
> > | EGL auto-detection... () 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork
-
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> > unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE
 -
> > I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++
-
> > I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl
-
> > I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> > vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp: In function 'int main(int, char**)': 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp:46:12: warning: unused variable 'x' [-Wunused-variable] 
> > |      EGLint x = 0; 
> > |             ^ 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork
-
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--
> > as-needed -Wl,-O1 -o egl egl.o   -lEGL 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to 
> `glxx_client_GetRenderbufferParameteriv'
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl20_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl11_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glintAttribPointer' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glxx_client_GenFramebuffers' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> >

[yocto] Antwort: Re: building qtbase for raspberry pi fails

2014-04-29 Thread Felix01 Fischer 
Unfortunately there is no library. After either "bitbake -c compile 
userland" or "bitbake userland" there are the source files (*.h *.c) and 
one named "*.c.o" but no *.o file exists

Vaduva alexandru  schrieb am 29.04.2014 
14:10:48:

> Von: Vaduva alexandru 
> An: Felix01 Fischer , 
> "yocto@yoctoproject.org" , 
> Datum: 29.04.2014 14:11
> Betreff: Re: [yocto] building qtbase for raspberry pi fails
> 
> Did you tried copying the glxx library into the rootfs lib directory?
> 
> On Tuesday, April 29, 2014 2:38 PM, Felix01 Fischer 
>  wrote:
> I've been able to narrow my problem futher down:
> 
> the meta-raspberrypi layer contains a bb called "userland_git.bb" 
> (meta-raspberrypi/recipes-graphics/userland/userland_git.bb). 
> the source for this layer is github.com/raspberrypi/userland.git. I 
> cloned this repository and searched for the undefined references.
> 
> This repository contains the source code for the ARM side libraries 
> used on Raspberry Pi. These typically are installed in /opt/vc/lib 
> and includes source for the ARM side code to interface to: EGL, 
> mmal, GLESv2, vcos, openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 
> 
> I had success! All my undefined references are defined in userland/
> interface/khronos/glxx/glxx_client.(h|c).
> 
> But still I haven't figured out how to get this build correctly so 
> qtbase can find and use it. 
> 
> Any suggestions?
> 
> Felix
> 
> 
> yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38:
> 
> > Von: Felix01 Fischer 
> 
> > An: yocto@yoctoproject.org, 
> > Datum: 25.04.2014 15:33 
> > Betreff: [yocto] building qtbase for raspberry pi fails 
> > Gesendet von: yocto-boun...@yoctoproject.org 
> > 
> > Hello everybody, 
> > first, I hope I have choosen the right mailing list for my problem. 
> > If not, please tell me.
> > 
> > I have problems getting Qt5 building and running on a raspberry pi 
> > (512 Mb Version).
> > I'm using today's master branch from yocto & meta-raspberrypi ( 
> > git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5 ).
> > Building without a change in qtbase doesn't work because the OpenGL 
> > Test fails ( the raspberry pi only suppports GLESv2). 
> > When building with a qtbase_X.Y.Z.bbappend and 
> > "PACKAGECCONFIG_append = " gles2" in order to use eglfs the mess 
beginns.
> > First, building qtbase fails because qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> > After including this manually in "meta-qt5/recipes-qt/qt5/
> > qtbase.inc" by adding the last line to configure 
> > do_configure() { 
> > 
> > [.] 
> > 
> > ${S}/configure -v \ 
> > -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \ 
> > 
> > [.] 
> > 
> > } 
> > 
> > 
> > the next error is the following: 
> > | EGL auto-detection... () 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork -
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> > unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE  -
> > I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++ -
> > I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl -
> > I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> > vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> > config.tests/qpa/egl/egl.cpp 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp: In function 'int main(int, char**)': 
> > | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> > egl.cpp:46:12: warning: unused variable 'x' [-Wunused-variable] 
> > |  EGLint x = 0; 
> > | ^ 
> > | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork -
> > mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> > build/tmp/sysroots/raspberrypi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--
> > as-needed -Wl,-O1 -o egl egl.o   -lEGL 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to 
> `glxx_client_GetRenderbufferParameteriv'
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl20_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `gl11_client_state_init' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glintAttribPointer' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glxx_client_GenFramebuffers' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glxx_buffer_info_get' 
> > | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> > lib/libEGL.so: undefined reference to `glDiscardFramebufferEXT' 
> > | /media/yocto_

Re: [yocto] building qtbase for raspberry pi fails

2014-04-29 Thread Vaduva alexandru 
Did you tried copying the glxx library into the rootfs lib directory?


On Tuesday, April 29, 2014 2:38 PM, Felix01 Fischer  
wrote:
 
I've been able to narrow my problem futher down:

the meta-raspberrypi layer contains a bb called "userland_git.bb"
(meta-raspberrypi/recipes-graphics/userland/userland_git.bb). 
the source for this layer is github.com/raspberrypi/userland.git.
I cloned this repository and searched for the undefined references.

This repository contains the source code for the ARM side libraries used
on Raspberry Pi. These typically are installed in /opt/vc/lib and includes
source for the ARM side code to interface to: EGL, mmal, GLESv2, vcos,
openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 

I had success! All my undefined references are defined in 
userland/interface/khronos/glxx/glxx_client.(h|c).

But still I haven't figured out how to get this build correctly so qtbase
can find and use it. 

Any suggestions?

Felix


yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38:


> Von: Felix01 Fischer 

> An: yocto@yoctoproject.org,  
> Datum: 25.04.2014 15:33 
> Betreff: [yocto] building qtbase for raspberry
pi fails 
> Gesendet von: yocto-boun...@yoctoproject.org 
> 
> Hello everybody, 
> first, I hope I have choosen the right mailing list for my problem. 
> If not, please tell me.
> 
> I have problems getting Qt5 building and running on a raspberry pi 
> (512 Mb Version).
> I'm using today's master branch from yocto & meta-raspberrypi
( 
> git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5
).
> Building without a change in qtbase doesn't work because the OpenGL 
> Test fails ( the raspberry pi only suppports GLESv2).  
> When building with a qtbase_X.Y.Z.bbappend and 
> "PACKAGECCONFIG_append = " gles2" in order to use eglfs
the mess beginns.
> First, building qtbase fails because qtbase-opensource-src-5.2.1/
> config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> After including this manually in "meta-qt5/recipes-qt/qt5/
> qtbase.inc" by adding the last line to configure  
> do_configure() {  
>   
> [.] 
> 
>     ${S}/configure -v \ 
> -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \ 
> 
> [.] 
> 
> } 
> 
>     
> the next error is the following:  
> | EGL auto-detection... ()  
> | arm-poky-linux-gnueabi-g++  -march=armv6
-mthumb-interwork -
> mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE
 -
> I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++ -
> I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl -
> I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> config.tests/qpa/egl/egl.cpp 
> | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> egl.cpp: In function 'int main(int, char**)': 
> | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> egl.cpp:46:12: warning: unused variable 'x' [-Wunused-variable] 
> |      EGLint x = 0; 
> |             ^ 
> | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork
-
> mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> build/tmp/sysroots/raspberrypi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--
> as-needed -Wl,-O1 -o egl egl.o   -lEGL 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_GetRenderbufferParameteriv'
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `gl20_client_state_init' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `gl11_client_state_init' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glintAttribPointer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_GenFramebuffers' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_buffer_info_get' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glDiscardFramebufferEXT' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_FramebufferTexture2D' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_IsRenderbuffer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_set_error' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_BindFramebuffer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/

Re: [yocto] building qtbase for raspberry pi fails

2014-04-29 Thread Felix01 Fischer 
I've been able to narrow my problem futher down:

the meta-raspberrypi layer contains a bb called "userland_git.bb" 
(meta-raspberrypi/recipes-graphics/userland/userland_git.bb).
the source for this layer is github.com/raspberrypi/userland.git. I cloned 
this repository and searched for the undefined references.

This repository contains the source code for the ARM side libraries used 
on Raspberry Pi. These typically are installed in /opt/vc/lib and includes 
source for the ARM side code to interface to: EGL, mmal, GLESv2, vcos, 
openmaxil, vchiq_arm, bcm_host, WFC, OpenVG. 

I had success! All my undefined references are defined in 
userland/interface/khronos/glxx/glxx_client.(h|c).

But still I haven't figured out how to get this build correctly so qtbase 
can find and use it.

Any suggestions?

Felix


yocto-boun...@yoctoproject.org schrieb am 25.04.2014 13:00:38:

> Von: Felix01 Fischer 
> An: yocto@yoctoproject.org, 
> Datum: 25.04.2014 15:33
> Betreff: [yocto] building qtbase for raspberry pi fails
> Gesendet von: yocto-boun...@yoctoproject.org
> 
> Hello everybody, 
> first, I hope I have choosen the right mailing list for my problem. 
> If not, please tell me.
> 
> I have problems getting Qt5 building and running on a raspberry pi 
> (512 Mb Version).
> I'm using today's master branch from yocto & meta-raspberrypi ( 
> git.yoctoproject.org ) and meta-qt5 ( github.com/meta-qt5/meta-qt5 ).
> Building without a change in qtbase doesn't work because the OpenGL 
> Test fails ( the raspberry pi only suppports GLESv2). 
> When building with a qtbase_X.Y.Z.bbappend and 
> "PACKAGECCONFIG_append = " gles2" in order to use eglfs the mess 
beginns.
> First, building qtbase fails because qtbase-opensource-src-5.2.1/
> config.tests/qpa/egl/egl.cpp cannot find "vcos_types.h"
> After including this manually in "meta-qt5/recipes-qt/qt5/
> qtbase.inc" by adding the last line to configure 
> do_configure() { 
> 
> [.] 
> 
> ${S}/configure -v \ 
> -I${STAGING_DIR_TARGET}/usr/include/interface/vcos/pthreads/ \ 
> 
> [.] 
> 
> } 
> 
> 
> the next error is the following: 
> | EGL auto-detection... () 
> | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork -
> mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> build/tmp/sysroots/raspberrypi -c -pipe  -O2 -pipe -g -feliminate-
> unused-debug-types -fvisibility-inlines-hidden -O2 -Wall -W -fPIE  -
> I../../../../qtbase-opensource-src-5.2.1/mkspecs/linux-oe-g++ -
> I../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl -
> I../../../../../../../../sysroots/raspberrypi/usr/include/interface/
> vcos/pthreads -I. -o egl.o ../../../../qtbase-opensource-src-5.2.1/
> config.tests/qpa/egl/egl.cpp 
> | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> egl.cpp: In function 'int main(int, char**)': 
> | ../../../../qtbase-opensource-src-5.2.1/config.tests/qpa/egl/
> egl.cpp:46:12: warning: unused variable 'x' [-Wunused-variable] 
> |  EGLint x = 0; 
> | ^ 
> | arm-poky-linux-gnueabi-g++  -march=armv6 -mthumb-interwork -
> mfloat-abi=softfp  -mfpu=vfp --sysroot=/media/yocto_build/qt5-raspb/
> build/tmp/sysroots/raspberrypi -Wl,-O1 -Wl,--hash-style=gnu -Wl,--
> as-needed -Wl,-O1 -o egl egl.o   -lEGL 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to 
`glxx_client_GetRenderbufferParameteriv'
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `gl20_client_state_init' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `gl11_client_state_init' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glintAttribPointer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_GenFramebuffers' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_buffer_info_get' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glDiscardFramebufferEXT' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_FramebufferTexture2D' 

> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_IsRenderbuffer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_set_error' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_BindFramebuffer' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> lib/libEGL.so: undefined reference to `glxx_client_GenRenderbuffers' 
> | /media/yocto_build/qt5-raspb/build/tmp/sysroots/raspberrypi/usr/
> l

Re: [yocto] quilt-native fails on tar version 1.27.1

2014-04-29 Thread Paul Eggleton 
On Tuesday 29 April 2014 13:23:36 Jegan Chandru wrote:
> On Tue, Apr 29, 2014 at 11:30 AM, Mirza Krak
> wrote:
> > I recently updated my Ubuntu PC to 14.04 LTS which broke yocto builds.
> > 
> > From what I can see is that there seems to be an issue with the tar
> > command and quilt-native recipe. But I am to newb to fix this. Do you guys
> > have any ideas?
>
> Only Yocto version 1.6 supports Ubuntu 14.04 LTS. I hope you are using
> that. if you are using <1.6 Ubuntu 14.04 LTS is not in supported distros.
> 
> http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#detailed-sup
> ported-distros
> http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#detailed-su
> pported-distros
> http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#detailed-su
> pported-distros
> 
> Also I found this,
> https://lists.yoctoproject.org/pipermail/yocto/2013-October/016540.html
> which makes ur problem a known issue.

FYI the tar 1.27 fix has been backported to the 1.4 "dylan" branch, however 
Angstrom might not have picked it up yet. Still, you may experience other 
problems with Ubuntu 14.04 with 1.4, so if you can upgrade to a newer major 
release you probably should.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] quilt-native fails on tar version 1.27.1

2014-04-29 Thread Mirza Krak 

On 2014-04-29 09:53, Jegan Chandru wrote:

Hi,

Only Yocto version 1.6 supports Ubuntu 14.04 LTS. I hope you are using 
that. if you are using <1.6 Ubuntu 14.04 LTS is not in supported distros.

I am actually working with 1.4 so should probably update.


http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#detailed-supported-distros
http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#detailed-supported-distros
http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#detailed-supported-distros

Also I found this,
https://lists.yoctoproject.org/pipermail/yocto/2013-October/016540.html
which makes ur problem a known issue.

Great that it is an known problem!


HTH.

-JC

Thank you for the help.



On Tue, Apr 29, 2014 at 11:30 AM, Mirza Krak 
mailto:mirza.k...@hostmobility.com>> wrote:


Hi.

I recently updated my Ubuntu PC to 14.04 LTS which broke yocto builds.

From what I can see is that there seems to be an issue with the
tar command and quilt-native recipe. But I am to newb to fix this.
Do you guys have any ideas?

uname -a
Linux mirza-hm 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

tar --version
tar (GNU tar) 1.27.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by John Gilmore and Jay Fenlason.

Attached log.

-- 
Med Vänliga Hälsningar / Best Regards


***
Mirza Krak
Host Mobility AB
mirza.k...@hostmobility.com 
Anders Personsgatan 12, 416 64 Göteborg
Sweden
http://www.hostmobility.com
Direct: +46 31 31 32 704 
Phone: +46 31 31 32 700 
Fax: +46 31 80 67 51 
Mobile: +46 730 28 06 22 
***


--
___
yocto mailing list
yocto@yoctoproject.org 
https://lists.yoctoproject.org/listinfo/yocto




--
JCP


--
Med Vänliga Hälsningar / Best Regards

***
Mirza Krak
Host Mobility AB
mirza.k...@hostmobility.com
Anders Personsgatan 12, 416 64 Göteborg
Sweden
http://www.hostmobility.com
Direct: +46 31 31 32 704
Phone: +46 31 31 32 700
Fax: +46 31 80 67 51
Mobile: +46 730 28 06 22
***

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] quilt-native fails on tar version 1.27.1

2014-04-29 Thread Jegan Chandru 
Hi,

Only Yocto version 1.6 supports Ubuntu 14.04 LTS. I hope you are using
that. if you are using <1.6 Ubuntu 14.04 LTS is not in supported distros.

http://www.yoctoproject.org/docs/1.6/ref-manual/ref-manual.html#detailed-supported-distros
http://www.yoctoproject.org/docs/1.5/ref-manual/ref-manual.html#detailed-supported-distros
http://www.yoctoproject.org/docs/1.4/ref-manual/ref-manual.html#detailed-supported-distros

Also I found this,
https://lists.yoctoproject.org/pipermail/yocto/2013-October/016540.html
which makes ur problem a known issue.

HTH.

-JC


On Tue, Apr 29, 2014 at 11:30 AM, Mirza Krak wrote:

> Hi.
>
> I recently updated my Ubuntu PC to 14.04 LTS which broke yocto builds.
>
> From what I can see is that there seems to be an issue with the tar
> command and quilt-native recipe. But I am to newb to fix this. Do you guys
> have any ideas?
>
> uname -a
> Linux mirza-hm 3.11.0-20-generic #34-Ubuntu SMP Tue Apr 1 20:40:25 UTC
> 2014 x86_64 x86_64 x86_64 GNU/Linux
>
> tar --version
> tar (GNU tar) 1.27.1
> Copyright (C) 2013 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later  html>.
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
>
> Written by John Gilmore and Jay Fenlason.
>
> Attached log.
>
> --
> Med Vänliga Hälsningar / Best Regards
>
> ***
> Mirza Krak
> Host Mobility AB
> mirza.k...@hostmobility.com
> Anders Personsgatan 12, 416 64 Göteborg
> Sweden
> http://www.hostmobility.com
> Direct: +46 31 31 32 704
> Phone: +46 31 31 32 700
> Fax: +46 31 80 67 51
> Mobile: +46 730 28 06 22
> ***
>
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
>


-- 
JCP
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Binary {deb,rpm} package install without repackaging

2014-04-29 Thread Richard Leitner - SKIDATA 
Hi,
thanks for that hint!
I finally managed to install a "third party" deb package using the 
ROOTFS_POSTPROCESS_COMMAND [1] in my rootfs.bb recipe.
Although I not fully understand why the "--admindir" parameter is required when 
the "--root" parameter is given.

The ROOTFS_POSTPROCESS_COMMAND I'm using is:
ROOTFS_POSTPROCESS_COMMAND += "${STAGING_BINDIR_NATIVE}/dpkg 
--root=${IMAGE_ROOTFS}/ --admindir=${IMAGE_ROOTFS}/var/lib/dpkg/  -i 
/path/to/package.deb"

I think pretty the same command will work for rpm packages.

Can anybody of you explain to me why "--root" AND "--admindir" are required for 
dpkg to work correctly?

According to the dpkg manpage --admindir shouldn't be required when --root is 
given:
--admindir=dir
  Change default administrative directory,  which  contains
  many   files   that  give  information  about  status  of
  installed or uninstalled  packages,  etc.   (Defaults  to
  /var/lib/dpkg)

--root=dir
  Changing root changes instdir  to  dir  and  admindir  to
  dir/var/lib/dpkg.

best regards,
Richard

[1] 
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#var-ROOTFS_POSTPROCESS_COMMAND

> From: Gaurang Shastri [mailto:gmshas...@gmail.com] 
> Sent: Monday, April 28, 2014 11:45 AM
> To: Richard Leitner - SKIDATA
> Subject: Re: [yocto] Binary {deb,rpm} package install without repackaging
>
> Dear Richard,
> 
> Do you want to copy some of the RPM to final ROOTFS image before ROOTFS image 
> is created  or you want to install some of the RPM package before ROOTFS 
> image is created ??
> 
> ROOTFS_POSTPROCESS_COMMAND or ROOTFS_POSTINSTALL_COMMAND is the way to go.
> 
> I did however run into a problem when running my script. Using variable ${D} 
> in my ROOTFS_POSTINSTALL_COMMAND gives the “wrong” path - it points to 
> …/image and I’d expect it to contain the path to …/rootfs.
> It seem the variable isreplaced before my function is executed.
> 
> I solved this by using variable ${IMAGE_ROOTFS} instead.
> 
> //Gaurang Shastri
> 
> 
> 
> On Mon, Apr 28, 2014 at 1:29 PM, Richard Leitner - SKIDATA 
>  wrote:
> > Hi everybody,
> > I've got a question regarding the binary deb/rpm packages in yocto.
> > 
> > Is there any possibility to install a binary deb/rpm package in the rootfs 
> > build without repackaging it?
> > Naively I'm for example thinking of an option in the image recipe like:
> > ADDITIONAL_PACKAGES += "/path/to/package.{deb,rpm}"
> > 
> > The point is that all possible solutions I found using recipes are 
> > extracting and then repackaging the package.
> > Due to the fact that during the repackaging all meta data and 
> > {pre,post}{rm,inst} scripts of the original package are lost this is a 
> > "no-go" for me.
> > 
> > I'd appreciate any help and hints!
> > 
> > Thanks!
> > 
> > best regards,
> > Richard
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto