Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Trapanese <marcotrapanese@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error building Qt5Multimedia
Date: Tue, 18 Mar 2014 14:17:27 +0100	[thread overview]
Message-ID: <53284767.3040408@gmail.com> (raw)
In-Reply-To: <CAAXf6LVvo4VSgkHawfNuftrqW317QzQ8FO2c-1k33datwdpfSg@mail.gmail.com>


Hi Thomas,
here my output:

http://pastebin.com/4QkcJ97t

it seems it doesn't find gstreamer:

Checking for openal... no
Checking for alsa... yes
Checking for pulseaudio... no
Checking for gstreamer... no
Checking for resourcepolicy... no

It's strange because it's already built.
What might lead to different behaviors among different machines with the 
same buildroot clone and .config file?

Best regards
Marco

--

Il 18/03/2014 13:08, Thomas De Schampheleire ha scritto:
> Hi Marco,
>
> On Tue, Mar 18, 2014 at 12:07 PM, Marco Trapanese
> <marcotrapanese@gmail.com> wrote:
>> Il 17/03/2014 13:24, Thomas De Schampheleire ha scritto:
>>
>>> I created a build with your .config file, and did not have any error.
>>> libqgsttools is present in qt5multimedia itself:
>>> output/build/qt5multimedia-5.2.1/lib/libqgsttools_p.so.1.0.0
>>> output/build/qt5multimedia-5.2.1/lib/libqgsttools_p.so.1.0
>>> output/build/qt5multimedia-5.2.1/lib/libqgsttools_p.so.1
>>> output/build/qt5multimedia-5.2.1/lib/libqgsttools_p.so
>>> output/build/qt5multimedia-5.2.1/lib/libqgsttools_p.prl Did you do something
>>> special in your buildroot directory/repo ? Try starting from a clean
>>> environment: make clean all Best regards, Thomas
>>
>> Hi Thomas,
>> I tried to:
>>
>> 1) git clone again buildroot, in order to have a clean environment
>> 2) copy my .config file
>> 3) check it with make nconfig (without change anything)
>> 4) make
>>
>> It fails in the same way and under output/build/qt5multimedia-5.2.1/lib
>> there are no libqgsttools* files...
>> I can't understand why it fails only on my pc!
>>
> I have executed 'make qt5multimedia-dirclean qt5multimedia' now and
> pasted the output here:
> http://code.bulix.org/eei5jl-85857
>
> maybe it can be useful for you to analyze the problem on your machine.
>
> Best regards,
> Thomas
>

  reply	other threads:[~2014-03-18 13:17 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 [this message]
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
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=53284767.3040408@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