> Am 13.11.2015 um 03:48 schrieb Huang, Jie (Jackie) 
> <[email protected]>:
> 
> 
> 
>> -----Original Message-----
>> From: [email protected] 
>> [mailto:openembedded-devel-
>> [email protected]] On Behalf Of Christopher Larson
>> Sent: Friday, November 13, 2015 4:17 AM
>> To: [email protected]
>> Cc: Christopher Larson
>> Subject: [oe] [meta-oe][PATCH 2/5] talloc,libtevent,libtdb: depend on attr
>> 
>> From: Christopher Larson <[email protected]>
>> 
>> These will depend on libattr if it's available, and we need deterministic
>> builds. This fixes a build-deps failure which occurs when attr is built 
>> before
>> them. There's currently no configuration option to explicitly control this
>> dependency, and I don't know enough about waf to add such an option, so
>> unconditionally dep on it for now.
> 
> I added depends on libcap  for libtevent for the same reason days ago, but it 
> really concern
> me now, the 'libreplace' in these waf based packages check many packages(I see
> libbsd, libcap, libacl for now) existence then build with them if found, and 
> there
> is no configure option to disable them, does anyone has a better idea how to
> make waf build in deterministic way? Maybe we should disable the built-in
> libraries 'libreplace' or add a PACKAGECONFIG for it?

I dug for it (libcap) since I couldn't find any reference in wscript & co and 
finally a 
$ for l in tmp/sysroots/curie/usr/lib/lib*.so; do 
tmp/sysroots/x86_64-linux/usr/libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/4.9.3/arm-poky-linux-gnueabi-objdump
 -x $l; done | less
pointed the origins:

* libldap_r.so
* libsmbconf.so

Think it shouldn't be a dependency in tevent, but in openldap ...

I add it to my patch series - just wanted to let you know.

Wrt. libbsd - if libbsd is found, stdlcat etc. is used from there, otherwise 
own implementation via lib/replace is provided, similar for some attr calls - 
but they aren't used in tevent/talloc ...
Looks as if lib/replace is a poor maintained libnbcompat alike :)

Cheers
-- 
Jens Rehsack - [email protected]

-- 
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to