[yocto] RPATH invalid

bart.thoelen at telenet.be bart.thoelen at telenet.be
Fri Nov 28 00:49:40 PST 2014



----- Original Message -----
> From: "Paul Eggleton" <paul.eggleton at linux.intel.com>
> To: "bart thoelen" <bart.thoelen at telenet.be>
> Cc: yocto at yoctoproject.org
> Sent: Thursday, November 27, 2014 5:43:17 PM
> Subject: Re: [yocto] RPATH invalid
> 
> Hi there,
> 
> On Thursday 27 November 2014 17:24:09 bart.thoelen at telenet.be wrote:
> > I now the following issue pops up here and there, but I cannot find a
> > proper
> > answer on what is wrong.
> > 
> > I'm trying to build a custom created auto-tools package in yocto (daisy
> > release). I get this QA check error:
> > 
> > 
> > 
> > ERROR: QA Issue: package logctrl contains bad RPATH
> > /mnt/data/sources/dx2/yocto/dx2/yocto/build/tmp/sysroots/zynq-lc80dx-appl/u
> > sr/lib in file
> > /mnt/data/sources/dx2/yocto/dx2/yocto/build/tmp/work/armv7a-vfp-neon-poky-l
> > inux-gnueabi/logctrl/1.0.0-r0/packages-split/logctrl/usr/bin/logctrl ERROR:
> > QA run found fatal errors. Please consider fixing them.
> > ERROR: Function failed: do_package_qa
> > ERROR: Logfile of failure stored in:
> > /mnt/data/sources/dx2/yocto/dx2/yocto/build/tmp/work/armv7a-vfp-neon-poky-l
> > inux-gnueabi/logctrl/1.0.0-r0/temp/log.do_package.20691 ERROR: Task 10
> > (/mnt/data/sources/dx2/yocto/dx2/yocto/meta-nikon/recipes-core/logctrl/logc
> > trl_1.0.0.bb, do_package) failed with exit code '1'
> > 
> > I guess this must be passed via the configure - see configure log (ignore
> > --without-rpath):
> 
> It depends entirely on whether the configure script provides an option for
> this, it looks like this one either does not, or if it does it isn't called
> --without-rpath.
> 
> There are some hints here about how to solve this kind of problem in the
> general case:
> 
>   http://www.yoctoproject.org/docs/current/ref-manual/ref-manual.html#qa-issue-rpaths
> 
> Ultimately you'll need to dig into how this particular software's own
> build system is set up with regard to enabling RPATHs when compiling
> - usually it's a matter of stopping the appropriate arguments from being
> passed to the compiler/linker.

That is exactly what I was thinking as well.  I created the automake scripts myself, they all behave well
when I build project the 'the old-fashion' way - i.e. doing the configure and make manually.
The project is building in Buildroot without any problem.  I'm moving towards yocto now.  So I really need to understand 
what yocto does differently so that I can adapt my automake scripts.

Anyway, I could just disable the QA checks for RPATH - but this is not the way I like to work.

greets,

BartT.

> 
> Cheers,
> Paul
> 
> --
> 
> Paul Eggleton
> Intel Open Source Technology Centre
> 



More information about the yocto mailing list