All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/mesa3d: disable broken toolchains on nios2
Date: Wed, 29 Jul 2015 22:56:58 +0200	[thread overview]
Message-ID: <20150729225658.118936f0@free-electrons.com> (raw)
In-Reply-To: <1438198976-25523-2-git-send-email-bernd.kuhls@t-online.de>

Dear Bernd Kuhls,

On Wed, 29 Jul 2015 21:42:55 +0200, Bernd Kuhls wrote:

> diff --git a/package/mesa3d/Config.in b/package/mesa3d/Config.in
> index c702d0d..2926c89 100644
> --- a/package/mesa3d/Config.in
> +++ b/package/mesa3d/Config.in
> @@ -11,6 +11,9 @@ menuconfig BR2_PACKAGE_MESA3D
>  	select BR2_PACKAGE_LIBXCB if BR2_PACKAGE_XORG7
>  	depends on BR2_INSTALL_LIBSTDCPP
>  	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL
> +	# Triggers the _gp link issue in nios2
> +	depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201305
> +	depends on !BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII201405

You forgot to propagate these new dependencies to the comment about
toolchain dependencies. I've done that and applied, thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-07-29 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 19:42 [Buildroot] [PATCH 1/3] package/mesa3d: disable libva support Bernd Kuhls
2015-07-29 19:42 ` [Buildroot] [PATCH 2/3] package/mesa3d: disable broken toolchains on nios2 Bernd Kuhls
2015-07-29 20:56   ` Thomas Petazzoni [this message]
2015-07-29 19:42 ` [Buildroot] [PATCH 3/3] package/mesa3d: Fix dri config option Bernd Kuhls
2015-07-29 20:57   ` Thomas Petazzoni
2015-07-29 20:56 ` [Buildroot] [PATCH 1/3] package/mesa3d: disable libva support Thomas Petazzoni

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=20150729225658.118936f0@free-electrons.com \
    --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 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.