From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-02
Date: Thu, 3 Apr 2014 18:25:12 +0100 [thread overview]
Message-ID: <533D9978.3000404@imgtec.com> (raw)
In-Reply-To: <20140403063009.526E4101924@stock.ovh.net>
On 04/03/2014 07:30 AM, Thomas Petazzoni wrote:
> Build statistics for 2014-04-02
> network-manager-0.9.8.8 | 1
> mips64el | network-manager-0.9.8.8 | NOK | http://autobuild.buildroot.net/results/3b6a40c1683d0859a934e4d79e2048e97b193e94/
This failure is caused because when network-manager is going to be built
it detects that Qt has been installed, so it passes the option
--enable-qt, which enables the Qt examples. It doesn't build
network-manager with Qt support (don't get confused by the name), it
only causes the Qt example to be built.
The Qt example included in network-manager uses an operator which is
available only if Qt has been built with STL compatibility. This is the
description of the operator:
"This operator is only available if Qt is configured with STL
compatibility enabled."
From: http://qt-project.org/doc/qt-4.8/qstring.html#toStdString
So, to be able to build that network-manager Qt example and fix the
autobuild failure we need to select BR2_PACKAGE_QT_STL. Or, the other
option (and I think is the one that has more sense) is to pass
--disable-qt to the network-manager configure options.
--
Vincent
next prev parent reply other threads:[~2014-04-03 17:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-02 Thomas Petazzoni
2014-04-03 17:25 ` Vicente Olivert Riera [this message]
2014-04-03 17:33 ` Bernd Kuhls
2014-04-03 18:16 ` ANDY KENNEDY
2014-04-06 20:31 ` Yann E. MORIN
2014-04-06 22:34 ` Peter Korsgaard
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=533D9978.3000404@imgtec.com \
--to=vincent.riera@imgtec.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 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.