yajl: Installed (but unpackaged) file(s) found

yajl: Installed (but unpackaged) file(s) found

[Stuart Yoder]

The yajl package (from meta-oe) is a dependency for another package
I'm building, but am getting an error on 64-bit targets where libyajl
is missing.

I noticed this when running bitbake with -v

> [cut]
> Checking for unpackaged file(s): /local/home/b08248/Work/sdk-devel/build_p5020ds-
> 64b_release/tmp/sysroots/x86_64-linux/usr/bin/../lib/rpm/check-files /local/home/b08248/Work/sdk-
> devel/build_p5020ds-64b_release/tmp/work/ppc64e5500-fsl_networking-linux/yajl/2.0.4-r0/package
>
> warning: Installed (but unpackaged) file(s) found:
>         /usr/lib/.debug/libyajl.so.2.0.4
>         /usr/lib/libyajl.so
>         /usr/lib/libyajl.so.2
>         /usr/lib/libyajl.so.2.0.4
>         /usr/lib/libyajl_s.a
>
> [cut]

It looks like the yajl packages builds everything and puts it into /usr/lib.

However, the packaging code expects to see this in /usr/lib64.  See
this in the environment:

   FILES_yajl="/usr/bin/* /usr/sbin/* /usr/lib64/yajl/* ...

Ho do I get the yajl recipe to either a) build the files in lib64 or
b) package them from lib.

Thanks,
Stuart

Re: yajl: Installed (but unpackaged) file(s) found

[Burton, Ross]

On 1 May 2013 20:11, Stuart Yoder <b08248@gmail.com> wrote:
>    FILES_yajl="/usr/bin/* /usr/sbin/* /usr/lib64/yajl/* ...
>
> Ho do I get the yajl recipe to either a) build the files in lib64 or
> b) package them from lib.

Don't hard-code paths, instead use the symbols available in bitbake.conf:

FILES_yajl = "${bindir}/* ${sbindir}/* ${libdir}/yajl/*"

Ros

Re: yajl: Installed (but unpackaged) file(s) found

[Paul Eggleton]

On Thursday 02 May 2013 10:24:10 Burton, Ross wrote:
> On 1 May 2013 20:11, Stuart Yoder <b08248@gmail.com> wrote:
> >    FILES_yajl="/usr/bin/* /usr/sbin/* /usr/lib64/yajl/* ...
> > 
> > Ho do I get the yajl recipe to either a) build the files in lib64 or
> > b) package them from lib.
> 
> Don't hard-code paths, instead use the symbols available in bitbake.conf:
> 
> FILES_yajl = "${bindir}/* ${sbindir}/* ${libdir}/yajl/*"

You should also use FILES_${PN} rather than FILES_yajl.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: yajl: Installed (but unpackaged) file(s) found

[Stuart Yoder]

yajl/libyajl is a dependeny I have for another package I'm trying to
build so I'm not touching the yajl recipe at all.  In fact the
complete recipe is this:

---------------------------------
DESCRIPTION = "Yet Another JSON Library - A Portable JSON parsing and serializat
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://COPYING;md5=74f541bd9a2b6c8e5d0714bcdc327f32"

SRCREV = "fee1ebef9fa7dc0e9f5a23f37123b19b68c796ff"
SRC_URI = "git://github.com/lloyd/yajl.git"

S = "${WORKDIR}/git"

inherit cmake lib_package
---------------------------------

It's just my observation that there seems to be a discrepancy between
what is getting built and packaged.   Things get built in ./lib and
packaged from ./lib64.

Do I really need to explicitly define FILES_yajl in this recipe?   It
seems like yajl is not the only package that might have this kind of
issue.   I have this feeling that there might be some simpler fix, but
I'm a novice at Yocto.

Stuart

On Thu, May 2, 2013 at 4:36 AM, Paul Eggleton
<paul.eggleton@linux.intel.com> wrote:
> On Thursday 02 May 2013 10:24:10 Burton, Ross wrote:
>> On 1 May 2013 20:11, Stuart Yoder <b08248@gmail.com> wrote:
>> >    FILES_yajl="/usr/bin/* /usr/sbin/* /usr/lib64/yajl/* ...
>> >
>> > Ho do I get the yajl recipe to either a) build the files in lib64 or
>> > b) package them from lib.
>>
>> Don't hard-code paths, instead use the symbols available in bitbake.conf:
>>
>> FILES_yajl = "${bindir}/* ${sbindir}/* ${libdir}/yajl/*"
>
> You should also use FILES_${PN} rather than FILES_yajl.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre

Re: yajl: Installed (but unpackaged) file(s) found

[Burton, Ross]

On 2 May 2013 14:16, Stuart Yoder <b08248@gmail.com> wrote:
> It's just my observation that there seems to be a discrepancy between
> what is getting built and packaged.   Things get built in ./lib and
> packaged from ./lib64.

It looks like yajl is hard-coding "lib" but presumably your machine
configuration wants to use "lib64".   Basically, yalj should be
respecting the directories passed to it through the cmake class
instead of assuming it knows best.

Ross