On 09/24/2015 07:55 PM, Burton, Ross wrote:
On 24 September 2015 at 12:49, Jussi Kukkonen <jussi.kukko...@intel.com
<mailto:jussi.kukko...@intel.com>> wrote:
I'm not seeing this problem and gnutls.pc.in <http://gnutls.pc.in>
file looks ok to me. Any idea how I could reproduce this?
Also, just sedding them out of the resulting file seems suboptimal
compared to finding out where the path is coming from and fixing that,
so it would be good to see an analysis as to where the path comes from.
Last timeI fixed a number of those it exposed real problems or bad
assumptions in the makefiles.
Ross
For this case, or such cases that use pkg-config to compute paths for
LIBS (such as zlib), they have different behaviors:
* multilib enabled build:
$ bitbake gnutls -cdevshell
$ pkg-config --libs zlib
-L/buildarea/raid5/wfan/yocto/builds/poky-build/tmp/sysroots/qemux86-64/usr/lib64
-lz
* build w/o multilib
$ bitbake gnutls -cdevshell
$ pkg-config --libs zlib
-lz
This is where the buildpaths from for target pkgconfig files. Ideally it
should be fixed from pkg-config side, but just fix it with sed is
acceptable I think if the former is impossible.
I'll investigate more about that. Do you know where the difference from?
Thanks
Wenzong
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
