Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure with Vivante and QT5 w/ eglfs
Date: Fri, 4 Mar 2016 10:55:34 +0100	[thread overview]
Message-ID: <20160304095534.GA16799@kwain> (raw)

Hi all,

I've run into a build failure while compiling an image, when building
QT5. I made some build tests to narrow down the issue and found the
configuration leading to this: when compiling an image with both
BR2_PACKAGE_QT5BASE_EGLFS and BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11 the
build fails with the following error:

http://code.bulix.org/qxj1bn-92391?raw

I understand this configuration can't work, but as this leads to a
build issue we might need to think about a solution. We could disallow
such a configuration tuple, or fix the build.

Any idea?

Thanks,

Antoine

-- 
Antoine T?nart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160304/3840cc84/attachment.asc>

             reply	other threads:[~2016-03-04  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04  9:55 Antoine Tenart [this message]
2016-03-04 11:02 ` [Buildroot] Build failure with Vivante and QT5 w/ eglfs Gary Bisson
2016-03-04 11:13   ` Thomas Petazzoni
2016-03-04 13:10     ` Gary Bisson
2016-03-04 13:19       ` Thomas Petazzoni
2016-03-04 13:35         ` Gary Bisson
2016-03-04 13:43           ` Thomas Petazzoni
2016-03-04 13:50   ` Antoine Tenart
2016-03-04 13:58     ` Gary Bisson
2016-03-07 10:18       ` Antoine Tenart
2016-03-07 10:38         ` Gary Bisson
2016-03-04 14:45   ` Jérôme Pouiller

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=20160304095534.GA16799@kwain \
    --to=antoine.tenart@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