From: wenzong fan <wenzong.fan@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gnutls: cleanup buildpaths from gnutls.pc
Date: Fri, 25 Sep 2015 18:21:40 +0800 [thread overview]
Message-ID: <56052034.4000702@windriver.com> (raw)
In-Reply-To: <CAJTo0LaJeeLRqmADYQ2DNGWs9VxwJMCRViwSvEX84FEbqVVTYA@mail.gmail.com>
On 09/24/2015 07:55 PM, Burton, Ross wrote:
>
> On 24 September 2015 at 12:49, Jussi Kukkonen <jussi.kukkonen@intel.com
> <mailto:jussi.kukkonen@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
next prev parent reply other threads:[~2015-09-25 10:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 11:04 [PATCH] gnutls: cleanup buildpaths from gnutls.pc wenzong.fan
2015-09-24 11:49 ` Jussi Kukkonen
2015-09-24 11:55 ` Burton, Ross
2015-09-25 10:21 ` wenzong fan [this message]
2015-09-25 10:52 ` Burton, Ross
2015-09-25 4:48 ` wenzong fan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56052034.4000702@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox