Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] znc: needs gcc >= 4.7
Date: Tue, 1 Sep 2015 14:50:28 +0100	[thread overview]
Message-ID: <55E5AD24.7070305@imgtec.com> (raw)
In-Reply-To: <1441115011-20223-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On 09/01/2015 02:43 PM, Gustavo Zacarias wrote:
> Fixes:
> http://autobuild.buildroot.net/results/aba/aba13674fb3624e0bd6a3b1e17f28883e298c8ca/
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  package/znc/Config.in | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/package/znc/Config.in b/package/znc/Config.in
> index 4328c8b..154d4b0 100644
> --- a/package/znc/Config.in
> +++ b/package/znc/Config.in
> @@ -3,11 +3,13 @@ config BR2_PACKAGE_ZNC
>  	depends on BR2_INSTALL_LIBSTDCPP
>  	depends on BR2_USE_MMU # fork()
>  	depends on !BR2_STATIC_LIBS
> +	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_7
>  	help
>  	  Advanced IRC bouncer
>  
>  	  http://www.znc.in
>  
> -comment "znc needs a toolchain w/ C++, dynamic library"
> -	depends on !BR2_INSTALL_LIBSTDCPP || BR2_STATIC_LIBS
> +comment "znc needs a toolchain w/ C++, dynamic library, gcc >= 4.7"
> +	depends on !BR2_INSTALL_LIBSTDCPP || BR2_STATIC_LIBS || \
> +		!BR2_TOOLCHAIN_GCC_AT_LEAST_4_7
>  	depends on BR2_USE_MMU
> 

Reviewed-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>

Regards,

Vincent.

  parent reply	other threads:[~2015-09-01 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:43 [Buildroot] [PATCH] znc: needs gcc >= 4.7 Gustavo Zacarias
2015-09-01 13:49 ` Vicente Olivert Riera
2015-09-01 13:50 ` Vicente Olivert Riera [this message]
2015-09-01 20:02 ` 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=55E5AD24.7070305@imgtec.com \
    --to=vincent.riera@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox