Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] qt 5.02 not building
Date: Wed, 7 Aug 2013 17:11:37 +0200	[thread overview]
Message-ID: <20130807171137.3aa6865a@skate> (raw)
In-Reply-To: <77698A93A9334B5FBD062F0FE17E67D4@JohanW7>

Dear Sagaert Johan,

On Wed, 7 Aug 2013 16:30:40 +0200, Sagaert Johan wrote:

> make[1]: Entering directory `/home/buildroot12git/output/build/qt5base-5.0.2/config.tests/common/sse2'
> /home/buildroot12git/output/host/usr/bin/arm-buildroot-linux-uclibcgnueabi-g++ -c -pipe -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
> -D_FILE_OFFSET_BITS=64 -pipe -Os --sysroot=/home/buildroot12git/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot -msse2 -g
> -Wall -W -fPIE  -I../../../mkspecs/devices/linux-buildroot-g++ -I.
> -I/home/buildroot12git/output/host/usr/arm-buildroot-linux-uclibcgnueabi/sysroot/usr/include -o sse2.o sse2.cpp
> cc1plus: error: unrecognized command line option '-msse2'

Is the build *really* failing and aborting at this point? What you're
showing here is part of the tests that Qt does to find out the
capabilities of the compiler. Here, it tests whether it supports the
-msse2 option, which obviously isn't possible because you're building
for ARM.

So Qt will simply assume that SSE2 isn't available, and will continue
with other configuration tests.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-08-07 15:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-07 14:30 [Buildroot] qt 5.02 not building Sagaert Johan
2013-08-07 15:11 ` Thomas Petazzoni [this message]
2013-08-07 17:38   ` Sagaert Johan
2013-08-07 21:42     ` Thomas Petazzoni
2013-08-08 14:15       ` Sagaert Johan

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=20130807171137.3aa6865a@skate \
    --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