From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Qt5Multimedia
Date: Tue, 18 Mar 2014 15:45:47 +0100 [thread overview]
Message-ID: <53285C1B.9040201@gmail.com> (raw)
In-Reply-To: <CAAXf6LX-dJFpaOkMaCg0A4PD1FphzO8xbPbLWTyLTX3xmO+ELA@mail.gmail.com>
Thomas,
> You can go to output/build/qt5multimedia and try to re-execute the
> command mentioned in config.log related to the gstreamer test. Maybe
> you can debug based on that, maybe using 'strace -fo /tmp/out
> <command>' to check what kind of files it is looking for.
I issued:
cd
/home/marco/dev/buildroot/output/build/qt5multimedia-5.2.1/config.tests/gstreamer
strace -fo /tmp/out /home/marco/dev/buildroot/output/host/usr/bin/qmake
"CONFIG -= qt debug_and_release app_bundle lib_bundle"
/home/marco/dev/buildroot/output/build/qt5multimedia-5.2.1/config.tests/gstreamer
Project ERROR: gstreamer-0.10 development package not found
Here the strace output:
http://code.bulix.org/7oi5mj-85862
I'm not so expert to understand what's happening.
Unfortunately this feature is mandatory for my project.
Are we working on the same repo? 2014.05-git-00363-g3749143
Unless buildroot needs something outside it's own directory it's very
strange such a behavior.
For you information my host machine is:
Linux devrpi 3.2.0-4-686-pae #1 SMP Debian 3.2.51-1 i686 GNU/Linux
Marco
next prev parent reply other threads:[~2014-03-18 14:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 6:32 [Buildroot] Error building Qt5Multimedia Marco Trapanese
2014-03-17 12:24 ` Thomas De Schampheleire
2014-03-18 11:07 ` Marco Trapanese
2014-03-18 12:08 ` Thomas De Schampheleire
2014-03-18 13:17 ` Marco Trapanese
2014-03-18 13:22 ` Marco Trapanese
2014-03-18 13:50 ` Thomas De Schampheleire
2014-03-18 14:17 ` Marco Trapanese
2014-03-18 14:28 ` Thomas De Schampheleire
2014-03-18 14:45 ` Marco Trapanese [this message]
2014-03-18 15:53 ` Thomas De Schampheleire
2014-03-18 18:27 ` Thomas Petazzoni
2014-03-19 5:31 ` Marco Trapanese
2014-03-20 19:25 ` Marco Trapanese
2014-03-20 20:16 ` Thomas De Schampheleire
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=53285C1B.9040201@gmail.com \
--to=marcotrapanese@gmail.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