From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR:Qt doesn't compile
Date: Thu, 15 Jul 2010 15:44:15 +0200 [thread overview]
Message-ID: <20100715154415.0e3ab363@surf> (raw)
In-Reply-To: <L5LNV3$BD4F538B66E3CB48DC7DF51A238DA643@aruba.it>
On Thu, 15 Jul 2010 14:54:39 +0200
"Luca Ceresoli" <list@lucaceresoli.net> wrote:
> > Creating qmake. Please wait...
> > make[1]: Entering directory
> > `/home/noy/buildroot/output/build/qt-everywhere-opensource-src-4.6.2/qmake'
> > make[1]: Leaving directory
> > `/home/noy/buildroot/output/build/qt-everywhere-opensource-src-4.6.2/qmake'
> > MySQL support cannot be enabled due to functionality tests!
> > Turn on verbose messaging (-v) to ./configure to see the final
> > report. If you believe this message is in error you may use the
> > continue switch (-continue) to ./configure to continue.
> > make: ***
> > [/buildroot/output/build/qt-everywhere-opensource-src-4.6.2/.configured]
> > Error 101
>
> Have a look to this bug report, I suspect it's the same problem you
> hit. There's a patch that could work.
>
> https://bugs.busybox.net/show_bug.cgi?id=2221
I'm currently looking at this problem (that I managed to reproduce).
The patch in 2221 is almost correct, but not sufficient. The dependency
is on "mysql_client" and not "mysql", and even after that, there are
build issues due to the fact that mysql headers and libraries are
installed in $(STAGING_DIR)/usr/include/mysql and
$(STAGING_DIR)/usr/lib/mysql.
I'm currently looking into this.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-07-15 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 12:54 [Buildroot] BR:Qt doesn't compile Luca Ceresoli
2010-07-15 13:44 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-13 6:27 Nataraj S Narayan
2010-07-13 8:43 ` Nataraj S Narayan
2010-07-16 22:04 ` 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=20100715154415.0e3ab363@surf \
--to=thomas.petazzoni@free-electrons.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