All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt5 and gpu-viv-bin-mx6q problem
Date: Thu, 27 Feb 2014 16:50:32 -0700	[thread overview]
Message-ID: <530FCF48.8000401@boundarydevices.com> (raw)
In-Reply-To: <530FA36B.1010003@mind.be>

On 02/27/2014 01:43 PM, Arnout Vandecappelle wrote:
> On 02/27/14 21:42, Eric Nelson wrote:
>> Hi Arnout,
>>
>> On 02/27/2014 01:16 PM, Arnout Vandecappelle wrote:
>>> On 02/27/14 09:22, Massimiliano Marretta wrote:
>>>> Dear,
>>>>
>>>> <snip>
>>>>
>>>> - If I use the last buildroot linaro toolchain 4.8-2013.09, the system
>>>> not start because the kernel is to old ( 3.0.35 ).
>>>> - If I use the toolchain linaro-4.7-2013.01 the Qt5 qmlscene exit without
>>>> message and gpu-viv-bin-mx6q examples not start with the message program
>>>> not found.
>>>
>>>    I think that gpu-viv-bin-mx6q are softfp libraries, so they won't work
>>> with Linaro (hardfp) toolchains. I'm surprised that qt5 builds at all in
>>> that case...
>>>
>> The latest patches (on -next) allow for either hardfp or softfp:
>>
>>      http://git.buildroot.net/buildroot/commit/package/freescale-imx/gpu-viv-bin-mx6q?h=next&id=b0b72591d74c1a84b8c1b2e1990a2fe1dfe8c4ab
>
>   Yes, but the OP mentioned that he uses 2013.11 in the text you snipped.
>

Oops.

  reply	other threads:[~2014-02-27 23:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  8:22 [Buildroot] Qt5 and gpu-viv-bin-mx6q problem Massimiliano Marretta
2014-02-27 20:16 ` Arnout Vandecappelle
2014-02-27 20:42   ` Eric Nelson
2014-02-27 20:43     ` Arnout Vandecappelle
2014-02-27 23:50       ` Eric Nelson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-02-27 21:40 Massimiliano Marretta
2014-02-28  0:11 ` Eric Nelson
2014-02-28  9:12 Massimiliano Marretta

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=530FCF48.8000401@boundarydevices.com \
    --to=eric.nelson@boundarydevices.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 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.