From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5]ERROR: QA Issue: qt...: The compile log indicates that host include and/or library paths were used
Date: Fri, 25 Apr 2014 14:38:15 +0200 [thread overview]
Message-ID: <20140425123815.GV2486@jama> (raw)
In-Reply-To: <ljcuv7$kr2$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
On Fri, Apr 25, 2014 at 08:22:30AM +0200, Neuer User wrote:
> With the latest version of the meta-qt5 the above error message is
> generated in the qa process.
>
> Environment: Ubuntu 12.04, Yocto "master-next", meta-qt5 branch
> jansa/5.3.0-beta1, platform: imx6
>
> See also here:
> https://community.freescale.com/docs/DOC-100419#comment-10891
0005-qt_module-Fix-pkgconfig-replacement.patch needs to be reworked
after it was (possibly partially resolved) changed in
eaefbe3 snuff -L/-I with system paths when installing meta files
a33afed de-duplicate setup of libdir replacement in prl files
aa20e7f reshuffle code for clarity
ee86ce8 don't attempt to replace include paths in meta files
See:
https://github.com/meta-qt5/meta-qt5/commit/5872d999583268a220cc3f033dba3eec34cd2d69
> Anybody knows, what's the problem?
>
> Latest good revision was: 92be18a
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
prev parent reply other threads:[~2014-04-25 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 6:22 [meta-qt5]ERROR: QA Issue: qt...: The compile log indicates that host include and/or library paths were used Neuer User
2014-04-25 12:38 ` Martin Jansa [this message]
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=20140425123815.GV2486@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.