All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt5: Disable on MIPS64 BigEndian n64 platforms
Date: Fri, 29 Nov 2013 15:28:03 +0000	[thread overview]
Message-ID: <5298B283.8070401@imgtec.com> (raw)
In-Reply-To: <1385738600-13376-1-git-send-email-Vincent.Riera@imgtec.com>

On 11/29/2013 03:23 PM, Vicente Olivert Riera wrote:
> qt5base fails to compile on MIPS64 BigEndian n64 platforms because there
> are multiple calls to some functions that are disabled. Since every Qt5
> package depends on qt5base we can disable Qt5 entirely. This is a quick
> fix for the next release. In the meantime, a proposed patch to fix this
> problem has already been sent to Qt:
>
> https://bugreports.qt-project.org/browse/QTBUG-35228
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>   package/qt5/Config.in |    1 +
>   1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/package/qt5/Config.in b/package/qt5/Config.in
> index 42724dc..b92d329 100644
> --- a/package/qt5/Config.in
> +++ b/package/qt5/Config.in
> @@ -9,6 +9,7 @@ menuconfig BR2_PACKAGE_QT5
>   	depends on BR2_INET_IPV6
>   	depends on BR2_TOOLCHAIN_HAS_THREADS
>   	depends on !BR2_PACKAGE_QT
> +	depends on !BR2_mips64 || !BR2_MIPS_NABI64
>   	help
>   	  This option enables the Qt5 framework. Sub-options allow to
>   	  select which modules should be built.
>

Acked-by: Markos Chandras <markos.chandras@imgtec.com>

-- 
markos

  reply	other threads:[~2013-11-29 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 15:23 [Buildroot] [PATCH] qt5: Disable on MIPS64 BigEndian n64 platforms Vicente Olivert Riera
2013-11-29 15:28 ` Markos Chandras [this message]
2013-11-29 18:44 ` Peter Korsgaard

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=5298B283.8070401@imgtec.com \
    --to=markos.chandras@imgtec.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.