From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: Disable passing of -isystem flag in CXXFLAGS
Date: Wed, 5 Oct 2016 07:12:24 +0000 [thread overview]
Message-ID: <1475651525.5303.9.camel@synopsys.com> (raw)
In-Reply-To: <1475225741.6467.6.camel@synopsys.com>
Hi Thomas, Arnout,
On Fri, 2016-09-30 at 11:55 +0300, Alexey Brodkin wrote:
> Hi?Arnout,
>
> On Thu, 2016-09-29 at 23:34 +0200, Arnout Vandecappelle wrote:
> >
> >
> > On 29-09-16 23:05, Arnout Vandecappelle wrote:
> > >
> > >
> > >
> > >
> > > On 28-09-16 10:54, Alexey Brodkin wrote:
> > > >
> > > >
> > > > So it all boils down to:
> > > > 1) "pkg-config" case:
> > > > --------------------->8--------------------
> > > > PKG_CONFIG_LIBDIR=${PKG_CONFIG_LIBDIR:-/XXX/output/host/usr/arc-buildroot-linux-
> > > > uclibc/sysroot/usr/lib/pkgconfig}
> > > > PKG_CONFIG_SYSROOT_DIR=${PKG_CONFIG_SYSROOT_DIR:-/XXX/output/host/usr/arc-buildroot-linux-uclibc/sysroot}
> > > > ./output/host/usr/bin/pkgconf --libs icu-i18n
> > > > -licui18n -L/XXX/output/host/usr/arc-buildroot-linux-uclibc/sysroot/usr/lib -licuuc -licudata
> > > > --------------------->8--------------------
> > > >
> > > > 2. Pure "pkgconf" case:
> > > > --------------------->8--------------------
> > > > ./output/host/usr/bin/pkgconf --libs icu-i18n
> > > > -licui18n -licuuc -licudata
> > > > --------------------->8--------------------
> > >
> > > ?Your pure pkgconf case is using the host icu-i18n, that's why the -L flag is
> > > missing. The host icu-i18n doesn't have a -L bit in its Libs: stanza.
> >
> > ?Hm, actually, icu-uc.pc *does* have a -L bit in its Libs: stanza. But for the
> > host, I guess it recognizes that ${libdir} == /usr/lib so it can be eliminated.
> > So perhaps that can be extended to cover a sysroot as well.
> >
> > ?BTW, I did a quick test with pkgconf 1.0.1 and it still behaves the same.
>
> Shall we then file an issue here?https://github.com/pkgconf/pkgconf/issues??
I'm wondering if there're any other thoughts on this one?
We're seeing more and more instances of that problem, for example with
qt5serialport?here?http://autobuild.buildroot.net/results/b14/b143bc806d45a91d52c43fa49227e88dc8a105d5/
So if there're no objections we may apply this one and see if it breaks anything
while we're far enough from the next BR release and in the worst case we'll just revert it
further down the line.
-Alexey
next prev parent reply other threads:[~2016-10-05 7:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 14:58 [Buildroot] [PATCH] qt5: Disable passing of -isystem flag in CXXFLAGS Alexey Brodkin
2016-09-23 22:11 ` Arnout Vandecappelle
2016-09-26 11:30 ` Alexey Brodkin
2016-09-27 22:33 ` Arnout Vandecappelle
2016-09-28 8:54 ` Alexey Brodkin
2016-09-29 21:05 ` Arnout Vandecappelle
2016-09-29 21:34 ` Arnout Vandecappelle
2016-09-30 8:55 ` Alexey Brodkin
2016-10-05 7:12 ` Alexey Brodkin [this message]
2016-09-30 8:54 ` Alexey Brodkin
2016-09-28 8:57 ` Thomas Petazzoni
2016-09-29 21:30 ` Arnout Vandecappelle
2016-10-05 8:01 ` Thomas Petazzoni
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=1475651525.5303.9.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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