Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Bruce Ashfield]

On 13-08-24 11:32 PM, Elvis Dowson wrote:

Hi Bruce,

On Aug 25, 2013, at 4:57 AM, Bruce Ashfield  wrote:


I created a new qemuarmhf.conf, to build using armv7a vfp and neon.

In the linux-yocto_3.8.bb recipe, I explicitly specified 
SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.

For some reason, it still refuses to build using kernel 3.8, and keeps 
defaulting to 3.4.52.

I know I can over-ride it in my local.conf by setting a PREFERRED_VERSION_virtual/linux 
="3.8" , but I'd like to know what I've missed, to get it to work by default, 
without setting the over-ride in my local.conf.


Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still 
picks up linux-yocto_3.4.bb recipe!



Try 3.8%, you need to match on the version completely, and it is 3.8, not
just 3.8.


Ok, I forgot about that!

Another quick question, why is it that when I create a new qemuarmhf.conf 
machine configuration, it doesn't automatically pick up the latest 
linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe?



Are you working off master ?

Since you set the compatibility, it should have been picked. But something
else must be changed in your layers, since if you didn't add
3.4 compatibility via bbappends, it never would have been selected
at all.

Cheers,

Bruce


Best regards,

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



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

Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

Hi Bruce,

On Aug 25, 2013, at 4:57 AM, Bruce Ashfield  wrote:

>>> I created a new qemuarmhf.conf, to build using armv7a vfp and neon.
>>> 
>>> In the linux-yocto_3.8.bb recipe, I explicitly specified 
>>> SRCREV_machine_qemuarmhf and added qemuarmhf to the list of 
>>> COMPATIBLE_MACHINES.
>>> 
>>> For some reason, it still refuses to build using kernel 3.8, and keeps 
>>> defaulting to 3.4.52.
>>> 
>>> I know I can over-ride it in my local.conf by setting a 
>>> PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've 
>>> missed, to get it to work by default, without setting the over-ride in my 
>>> local.conf.
>> 
>> Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still 
>> picks up linux-yocto_3.4.bb recipe!
>> 
> 
> Try 3.8%, you need to match on the version completely, and it is 3.8, not
> just 3.8.

Ok, I forgot about that! 

Another quick question, why is it that when I create a new qemuarmhf.conf 
machine configuration, it doesn't automatically pick up the latest 
linux-yocto_3.8.bb recipe? Why does it attempt to use the 3.4 recipe?

Best regards,

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

[yocto] Packaging 2.6.39 kernel also includes 3.5 kernel..! Why.?

[Sudhangathan B S]

I have asked this question in the Gumstix-Users mailing list before, but
got no reply..
So just checking out here..!

Why does Yocto include 3.5.0/ kernel folder too in the lib/modules/
directory, while I have enabled 2.6.39 kernel recipe..?? I just extracted
the file gumstix-console-image-overo-20130821225106.rootfs.tar.bz2 i  Now
see there are two folders in the lib/modules/ directory namely "3.5.0/" and
"2.6.39/" .

Should it be like that.. Or is there a confusion internally..??
Can I have an explanation please...?? How should I correct.?

When booting, on the console i don't see anything more than "Done booting
the kernel..." The serial port set in the uboot env is ttyO2.. This is
correct for 2.6.39 kernel..! Isn't it..?


This is the configuration:

OE Build Configuration:
BB_VERSION= "1.15.2"
TARGET_ARCH   = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE   = "overo"
DISTRO= "poky"
DISTRO_VERSION= "1.2.1"
TUNE_FEATURES = "armv7a vfp neon cortexa8"
TARGET_FPU= "vfp-neon"
meta
meta-yocto= "(nobranch):846b7c388738f382e83576e77b705aa547c1dd9b"
meta-gnome
meta-oe
meta-xfce = "(nobranch):e77646bc2cf905fd671fc5c19ab6fd17f9b94b3f"
meta-gumstix  = "(nobranch):9293374e7a6dba72ac3b7350659f9a1877739b39"
meta-dese_iisc= "(nobranch):846b7c388738f382e83576e77b705aa547c1dd9b"

This is my overo.inc file:==

desen555@desen555-UStudio:~/yocto/poky$ cat
meta-dese_iisc/conf/machine/overo.inc
require conf/machine/include/omap3.inc

EXTRA_IMAGEDEPENDS = "u-boot-sakoman"

PREFERRED_PROVIDER_virtual/bootloader = "u-boot-sakoman"
UBOOT_MACHINE = "omap3_overo_config"
#PREFERRED_VERSION_pn-u-boot = "2011.12"

#PREFERRED_PROVIDER_virtual/kernel = "linux-omap3"
PREFERRED_PROVIDER_ntp = "ntp"
#PREFERRED_PROVIDER_virtual/kernel = "linux-sakoman"
PREFERRED_PROVIDER_virtual/kernel = "linux-omap-pm"

PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
XSERVER = "xserver-xorg \
   xf86-input-evdev \
   xf86-input-mouse \
   xf86-video-omapfb \
   xf86-input-keyboard"

PREFERRED_PROVIDER_jpeg = "libjpeg-turbo"
PREFERRED_PROVIDER_jpeg-native = "libjpeg-turbo-native"

SERIAL_CONSOLE = "115200 ttyO2"

IMAGE_FSTYPES += "tar.bz2"

MKUBIFS_ARGS = "-m 2048 -e 129024 -c 4044"
UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512"

UBI_VOLNAME = "rootfs"

MACHINE_EXTRA_RDEPENDS = "omap3-writeprom"
MACHINE_EXTRA_RRECOMMENDS = " kernel-modules"

MACHINE_FEATURES = "kernel26 alsa apm ext3 screen usbgadget usbhost vfat
wifi"

-
Sudhangathan BS
Ph:(+91) 9731-905-205
-
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Bruce Ashfield]

On Sat, Aug 24, 2013 at 2:06 PM, Elvis Dowson  wrote:
>
> On Aug 24, 2013, at 10:00 PM, Elvis Dowson  wrote:
>
>> I created a new qemuarmhf.conf, to build using armv7a vfp and neon.
>>
>> In the linux-yocto_3.8.bb recipe, I explicitly specified 
>> SRCREV_machine_qemuarmhf and added qemuarmhf to the list of 
>> COMPATIBLE_MACHINES.
>>
>> For some reason, it still refuses to build using kernel 3.8, and keeps 
>> defaulting to 3.4.52.
>>
>> I know I can over-ride it in my local.conf by setting a 
>> PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've 
>> missed, to get it to work by default, without setting the over-ride in my 
>> local.conf.
>
> Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still 
> picks up linux-yocto_3.4.bb recipe!
>

Try 3.8%, you need to match on the version completely, and it is 3.8, not
just 3.8.

Bruce

> What am I failing to set or configure additionally to get it to work, as 
> intended?
>
> Best regards,
>
> Elvis Dowson
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

On Aug 24, 2013, at 10:00 PM, Elvis Dowson  wrote:

> I created a new qemuarmhf.conf, to build using armv7a vfp and neon. 
> 
> In the linux-yocto_3.8.bb recipe, I explicitly specified 
> SRCREV_machine_qemuarmhf and added qemuarmhf to the list of 
> COMPATIBLE_MACHINES.
> 
> For some reason, it still refuses to build using kernel 3.8, and keeps 
> defaulting to 3.4.52.
> 
> I know I can over-ride it in my local.conf by setting a 
> PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've 
> missed, to get it to work by default, without setting the over-ride in my 
> local.conf.

Weird, even after setting PREFERRED_VERSION_virtual/linux ="3.8", it still 
picks up linux-yocto_3.4.bb recipe!

What am I failing to set or configure additionally to get it to work, as 
intended?

Best regards,

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

[yocto] linux-yocto defaulting to 3.4.52 for new qemuarmhf.conf

[Elvis Dowson]

Hi,
  I created a new qemuarmhf.conf, to build using armv7a vfp and neon. 

In the linux-yocto_3.8.bb recipe, I explicitly specified 
SRCREV_machine_qemuarmhf and added qemuarmhf to the list of COMPATIBLE_MACHINES.

For some reason, it still refuses to build using kernel 3.8, and keeps 
defaulting to 3.4.52.

I know I can over-ride it in my local.conf by setting a 
PREFERRED_VERSION_virtual/linux ="3.8" , but I'd like to know what I've missed, 
to get it to work by default, without setting the over-ride in my local.conf.

Thanks!

Best regards,

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

Re: [yocto] [DYLAN] RPATH issue with qt5's qtwebkit

[Richard Purdie]

On Sat, 2013-08-24 at 15:06 +0200, Erik Botö wrote:
> On Sat, Aug 24, 2013 at 3:36 AM, Trevor Woerner
>  wrote:
> > Hi,
> >
> > When I try to include "qtwebkit" in my image from the "dylan" branch I end
> > up
> > with the following QA do_package_qa error [note that this does not happen
> > with "master"]:
> >
> > ERROR: QA Issue: package qtwebkit contains bad RPATH
> > /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> > in file
> > /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/packages-split/qtwebkit/usr/lib/qt5/libexec/QtWebProcess
> >
> > And the QA test is correct. When I "objdump -x" this binary I get:
> >
> > Dynamic Section:
> >   NEEDED   libQt5WebKitWidgets.so.5
> >   NEEDED   libQt5WebKit.so.5
> >   NEEDED   libQt5Widgets.so.5
> >   NEEDED   libQt5Core.so.5
> >   NEEDED   libstdc++.so.6
> >   NEEDED   libc.so.6
> >   RPATH
> > /home/trevor/build/yocto/tmp/rdk/work/armv5te-rdk-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> >
> > Can anyone suggest any fixes or patches? Note I'm using 5.0.2.
> 
> Try adding a .bbappend with the following content:
> 
> #
> DEPENDS += "chrpath-replacement-native"
> EXTRANATIVEPATH += "chrpath-native"
> 
> PRINC := "${@int(PRINC) + 1}"
> 
> do_install_append() {
> # Remove rpath from the offending binaries
> chrpath -d ${D}${OE_QMAKE_PATH_LIBEXECS}/QtWebProcess
> }
> #
> 
> That should do it.
> 
> Is this something everyone building qtwebkit is seeing? I had just
> assumed that it had something to do with other changes I do to
> meta-qt5, but if it affect everyone I guess it could be done in
> meta-qt5 instead of local bbappends.

The above is a workaround, the proper fix is to track down why this is
making its way in there in the first place and fix the problem at
source.

Cheers,

Richard

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

Re: [yocto] an error when adding "snappy" package

[Gary Thomas]

On 2013-08-23 14:36, Reeve Yang wrote:

Hi Gary, the uri.inc is just my include file to point to local package storage location, 
and "native" extend I have taken it out.

Yeah, I figured it out this is rpm specific. If I change the 
site-packages/smart/backends/rpm/pm.py, line 280 to:

 self.rpmout = reader(open(rpmoutpath), errors = "ignore")

The error would be gone and my tarball is created successfully. My question is, why yocto 
assume default encoding is ascii? Is there anyway for me to specify the encoding in 
"utf8"?


This sounds like a bug to me.  It would be best if you file it as
such with bugzilla so it gets looked at properly (I'm not the one
to do that, sorry)


On Thu, Aug 22, 2013 at 1:12 PM, Gary Thomas mailto:g...@mlbassoc.com>> wrote:

On 2013-08-22 13:30, Gary Thomas wrote:

On 2013-08-21 16:03, Reeve Yang wrote:

Hi Grus,

I have been trying to add google snappy package into yocto 
(https://code.google.com/p/__snappy/ ), here 
is my receipt file, nothing
special:

SUMMARY = "Snappy is a compression/decompression library."
DESCRIPTION = ""
HOMEPAGE="https://code.google.__com/p/snappy 
"
SECTION = "console/utils"
LICENSE = "BSD"
LIC_FILES_CHKSUM = 
"file://COPYING;md5=__b2c8cef4261c6377dcae51b2903d70__4b"
PR = "r0"
require ../uri.inc


What's in this file (uri.inc)?

SRC_URI = "${URIPREFIX}/snappy-${PV}.__tar.gz"
SRC_URI[md5sum] = "__c8f3ef29b5281e78f4946b2d739cea__4f"
SRC_URI[sha256sum] = 
"__1fa82bc588bb93fa74dfc0e2e9b7d6__3b6e2a20ede323ef42bf0af0f94767__6160"
inherit autotools
BBCLASSEXTEND = "native"
do_compile() {
  oe_runmake all
}
do_install() {
  oe_runmake DESTDIR=${D} install
}
BBCLASSEXTEND = "native"


Do you need this (is snappy-native used)?


Note: I had no trouble building and installing this into a IPK based image, 
so
it may be something special with the RPM packaging (which I don't use).




The package was built successfully, but when I try to build 
core-image-lsb (my own image but similar), I got following error:

|  528:Installing libsnappy1  
##__## [ 44%]
| Traceback (most recent call last):
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__site-packages/smart/backends/__rpm/pm.py",
 line 312, in __call__
| self._process_rpmout()
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__site-packages/smart/backends/__rpm/pm.py",
 line 297, in _process_rpmout
| output = self.rpmout.read()
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__codecs.py",
 line 477, in read
| newchars, decodedbytes = self.decode(data, self.errors)
| UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in 
position 740: ordinal not in range(128)
|
| Traceback (most recent call last):
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__site-packages/smart/backends/__rpm/pm.py",
 line 312, in __call__
| self._process_rpmout()
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__site-packages/smart/backends/__rpm/pm.py",
 line 297, in _process_rpmout
| output = self.rpmout.read()
|   File 
"/home2/reeve-ws/yocto-dylan-__merge/build/tmp/sysroots/x86___64-linux/usr/lib/python2.7/__codecs.py",
 line 477, in read
| newchars, decodedbytes = self.decode(data, self.errors)
| UnicodeDecodeError: 'ascii' codec can't decode byte 0xa1 in 
position 740: ordinal not in range(128)
|
| ERROR: Function failed: do_rootfs (see 
/home2/reeve-ws/yocto-dylan-__merge/build/tmp/work/rp-poky-__linux/core-image-ssr/1.0-r0/__temp/log.do_rootfs.2751
 for further
information)
ERROR: Task 7 
(/home2/reeve-ws/yocto-dylan-__merge/meta-ericsson-ssr-rp/__recipes-core-image/core-image-__ssr.bb
  ,
do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4128 tasks of which 4114 didn't need 
to be rerun and 1 failed.
No currently running tasks (4128 of 4129)

Can anyone help me out?


_
yocto mailing list
yocto@yoctoproject.org 

Re: [yocto] [DYLAN] RPATH issue with qt5's qtwebkit

[Martin Jansa]

On Sat, Aug 24, 2013 at 03:06:21PM +0200, Erik Botö wrote:
> On Sat, Aug 24, 2013 at 3:36 AM, Trevor Woerner
>  wrote:
> > Hi,
> >
> > When I try to include "qtwebkit" in my image from the "dylan" branch I end
> > up
> > with the following QA do_package_qa error [note that this does not happen
> > with "master"]:
> >
> > ERROR: QA Issue: package qtwebkit contains bad RPATH
> > /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> > in file
> > /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/packages-split/qtwebkit/usr/lib/qt5/libexec/QtWebProcess
> >
> > And the QA test is correct. When I "objdump -x" this binary I get:
> >
> > Dynamic Section:
> >   NEEDED   libQt5WebKitWidgets.so.5
> >   NEEDED   libQt5WebKit.so.5
> >   NEEDED   libQt5Widgets.so.5
> >   NEEDED   libQt5Core.so.5
> >   NEEDED   libstdc++.so.6
> >   NEEDED   libc.so.6
> >   RPATH
> > /home/trevor/build/yocto/tmp/rdk/work/armv5te-rdk-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> >
> > Can anyone suggest any fixes or patches? Note I'm using 5.0.2.
> 
> Try adding a .bbappend with the following content:
> 
> #
> DEPENDS += "chrpath-replacement-native"
> EXTRANATIVEPATH += "chrpath-native"
> 
> PRINC := "${@int(PRINC) + 1}"
> 
> do_install_append() {
> # Remove rpath from the offending binaries
> chrpath -d ${D}${OE_QMAKE_PATH_LIBEXECS}/QtWebProcess
> }
> #
> 
> That should do it.
> 
> Is this something everyone building qtwebkit is seeing? I had just
> assumed that it had something to do with other changes I do to
> meta-qt5, but if it affect everyone I guess it could be done in
> meta-qt5 instead of local bbappends.

Yes I think everyone is seeing it, but in many distro configs bad RPATH
is only QA warning not error (that's why I was partially ignoring it
until now, concentrating on other issues).

You can see do_configure_append in qtwebkit.inc which is removing bad
rpath from qmake generated Makefile, this sometimes doesn't work, from
similar Makefile issue in qtjsondb I know that "sometimes" Makefile
generated in do_configure is regenerated later in do_compile or
do_install task, I'm not sure yet why, but that's what breaks similar
hack in qtjsondb_git.bb:do_configure_append().

Of course the real fix for both issues would be to fix .pri/.prf files
to prevent incorrect Makefile to be generated at all.

Regards,

> 
> Cheers
> Erik
> 
> 
> >
> > Best regards,
> > Trevor
> >
> > ___
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
> >
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com


signature.asc
Description: Digital signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] QEMU with ARM Cortex A9 hard float with NEON

[Elvis Dowson]

Hi,
  I'm trying to build a QEMU machine configuration with support for ARM 
Cortex A9, with hard float and neon support.

What should I specify in my qemuarmhf.conf machine file to enable a specific 
tune configuration defined in tune-cortexa9.inc ?

Best regards,

Elvis Dowson


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

Re: [yocto] [DYLAN] RPATH issue with qt5's qtwebkit

[Erik Botö]

On Sat, Aug 24, 2013 at 3:36 AM, Trevor Woerner
 wrote:
> Hi,
>
> When I try to include "qtwebkit" in my image from the "dylan" branch I end
> up
> with the following QA do_package_qa error [note that this does not happen
> with "master"]:
>
> ERROR: QA Issue: package qtwebkit contains bad RPATH
> /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> in file
> /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/packages-split/qtwebkit/usr/lib/qt5/libexec/QtWebProcess
>
> And the QA test is correct. When I "objdump -x" this binary I get:
>
> Dynamic Section:
>   NEEDED   libQt5WebKitWidgets.so.5
>   NEEDED   libQt5WebKit.so.5
>   NEEDED   libQt5Widgets.so.5
>   NEEDED   libQt5Core.so.5
>   NEEDED   libstdc++.so.6
>   NEEDED   libc.so.6
>   RPATH
> /home/trevor/build/yocto/tmp/rdk/work/armv5te-rdk-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
>
> Can anyone suggest any fixes or patches? Note I'm using 5.0.2.

Try adding a .bbappend with the following content:

#
DEPENDS += "chrpath-replacement-native"
EXTRANATIVEPATH += "chrpath-native"

PRINC := "${@int(PRINC) + 1}"

do_install_append() {
# Remove rpath from the offending binaries
chrpath -d ${D}${OE_QMAKE_PATH_LIBEXECS}/QtWebProcess
}
#

That should do it.

Is this something everyone building qtwebkit is seeing? I had just
assumed that it had something to do with other changes I do to
meta-qt5, but if it affect everyone I guess it could be done in
meta-qt5 instead of local bbappends.

Cheers
Erik


>
> Best regards,
> Trevor
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [DYLAN] RPATH issue with qt5's qtwebkit

[Richard Purdie]

On Fri, 2013-08-23 at 21:36 -0400, Trevor Woerner wrote:
> When I try to include "qtwebkit" in my image from the "dylan" branch I end up
> with the following QA do_package_qa error [note that this does not happen
> with "master"]:
> 
> ERROR: QA Issue: package qtwebkit contains bad RPATH 
> /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
>  in file 
> /home/trevor/build/yocto/tmp/dylan/work/armv5te-poky-linux-gnueabi/qtwebkit/5.0.2-r0.0/packages-split/qtwebkit/usr/lib/qt5/libexec/QtWebProcess
> 
> 
> And the QA test is correct. When I "objdump -x" this binary I get:
> 
> Dynamic Section:
>   NEEDED   libQt5WebKitWidgets.so.5
>   NEEDED   libQt5WebKit.so.5
>   NEEDED   libQt5Widgets.so.5
>   NEEDED   libQt5Core.so.5
>   NEEDED   libstdc++.so.6
>   NEEDED   libc.so.6
>   RPATH
> /home/trevor/build/yocto/tmp/rdk/work/armv5te-rdk-linux-gnueabi/qtwebkit/5.0.2-r0.0/build/lib
> 
> 
> Can anyone suggest any fixes or patches? Note I'm using 5.0.2.

Check the compile logs. Somewhere, something is passing a -rpath value
to the linker which results in this. You'll have to find out where it
gets passed in, then trace it back to the source of the problem.
Sometimes this can get added by libtool but there will still be
something on the commandline which triggers libtool to do that.

Cheers,

Richard




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

Re: [yocto] Installing yocto built qemu binaries and sdk toolchain to another machine

[Elvis Dowson]

On Aug 24, 2013, at 8:49 AM, Elvis Dowson  wrote:

> What should I do to relocate and install the qemu binaries and sdk toolchain 
> built using yocto, to another machine? 
> 
> The target machine has a fresh Ubuntu 12.04 installation, and I'd like to be 
> able to run the Yocto generated qemu binaries inside it.

I found the answer to this, the qemu images are located with the 
meta-toolchain-sdk, so copy over the generated kernel and rootfilesystem (ext3) 
images to the new machine, installing the toolchain SDK to /opt, and running 
the following commands on the target machine worked.

. '/opt/poky/1.4+snapshot/environment-setup-armv5te-poky-linux-gnueabi'
runqemu qemuarm zImage-qemuarm.bin core-image-minimal-qemuarm.rootfs.ext3

Best regards,

Elvis Dowson

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