From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11401] Impossible do build a qt program using kf5-networkmanager-qt with qmake
Date: Wed, 17 Oct 2018 16:11:24 +0000 [thread overview]
Message-ID: <bug-11401-163-ByIEpDkvAQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-11401-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=11401
--- Comment #11 from Pierre Ducroquet <pinaraf@pinaraf.info> ---
After analysis and some checks (thanks Nicolas for your availability on IRC) it
looks like there are two issues:
- a bug in extra-cmake-modules that generates invalid pri when cross-building
- wrong cmake settings on my side, thus putting files in wrong places
I am still working on it and confident a solution will be found by tomorrow.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2018-10-17 16:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 12:31 [Buildroot] [Bug 11401] New: Impossible do build a qt program using kf5-networkmanager-qt bugzilla at busybox.net
2018-10-16 13:21 ` [Buildroot] [Bug 11401] " bugzilla at busybox.net
2018-10-16 13:26 ` bugzilla at busybox.net
2018-10-16 13:29 ` bugzilla at busybox.net
2018-10-16 16:31 ` bugzilla at busybox.net
2018-10-17 6:15 ` bugzilla at busybox.net
2018-10-17 6:37 ` bugzilla at busybox.net
2018-10-17 6:39 ` bugzilla at busybox.net
2018-10-17 6:39 ` [Buildroot] [Bug 11401] Impossible do build a qt program using kf5-networkmanager-qt with qmake bugzilla at busybox.net
2018-10-17 6:57 ` bugzilla at busybox.net
2018-10-17 7:04 ` bugzilla at busybox.net
2018-10-17 7:11 ` bugzilla at busybox.net
2018-10-17 16:11 ` bugzilla at busybox.net [this message]
2024-06-15 14:48 ` bugzilla
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=bug-11401-163-ByIEpDkvAQ@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.