From: Patrick Noffke <patrick@noffke.me>
To: buildroot@busybox.net
Subject: [Buildroot] Qt 5.3.0 fails to build with eglfs (ti-glx) enabled, ARM platform (beaglebone black)
Date: Mon, 23 Jun 2014 14:43:22 -0500 [thread overview]
Message-ID: <3591081.u5CTo5tRRS@localhost.localdomain> (raw)
In-Reply-To: <4081522.HPB2TGLcVe@localhost.localdomain>
On Monday, June 23, 2014 02:10:50 PM Patrick Noffke wrote:
> Hello,
>
> I'm trying to build Qt 5.3.0 within buildroot, using the ti-gfx package and
> starting with the beaglebone black defconfig.
>
> The build fails when trying to link libQt5Widgets.5.3.0. This page
> (https://codereview.qt-project.org/#/c/79783/) made me think I might have
> success by enabling neon, which I did by editing the qt5base-0002-mkspecs-
> files.patch file as follows:
>
> +QMAKE_CFLAGS += $${BR_COMPILER_CFLAGS} -mfpu=neon -march=armv7-a
> +QMAKE_CXXFLAGS += $${BR_COMPILER_CXXFLAGS} -mfpu=neon
> -march=armv7-a +CONFIG += nostrip neon
>
> but it fails the same way with or without these changes.
>
> Has anyone else had this issue or found some way around it? Portions of my
> build log follow.
>
I found the problem thanks to this page (http://comments.gmane.org/gmane.linux.embedded.yocto.meta-freescale/8682). I had to remove libQt5* from output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib.
Hope this helps someone else!
Patrick
prev parent reply other threads:[~2014-06-23 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 19:10 [Buildroot] Qt 5.3.0 fails to build with eglfs (ti-glx) enabled, ARM platform (beaglebone black) Patrick Noffke
2014-06-23 19:43 ` Patrick Noffke [this message]
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=3591081.u5CTo5tRRS@localhost.localdomain \
--to=patrick@noffke.me \
--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.