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

Richard Purdie richard.purdie at linuxfoundation.org
Sat Aug 24 09:03:54 PDT 2013


On Sat, 2013-08-24 at 15:06 +0200, Erik Botö wrote:
> On Sat, Aug 24, 2013 at 3:36 AM, Trevor Woerner
> <trevor.woerner at linaro.org> 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




More information about the yocto mailing list