From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] liquid-dsp: blacklist CS powerpc toolchains
Date: Tue, 17 Nov 2015 17:24:57 -0300 [thread overview]
Message-ID: <564B8D19.9070508@zacarias.com.ar> (raw)
In-Reply-To: <20151117211943.3b638229@free-electrons.com>
On 17/11/15 17:19, Thomas Petazzoni wrote:
> You forgot to use the same dependencies in the comment, to avoid it
> being displayed in cases where the package can anyway not be enabled.
> I've applied to master after fixing this. Thanks!
>
> Thomas
Hi Thomas.
I believe that would be a no-op, since:
comment "liquid-dsp requires a (e)glibc/musl toolchain w/ dynamic library"
depends on !(BR2_TOOLCHAIN_USES_GLIBC ||
BR2_TOOLCHAIN_USES_MUSL) || BR2_STATIC_LIBS
It is a glibc toolchain (well, eglibc i believe, but same deal), and
glibc toolchains can't do static, so unreachable.
Regards.
prev parent reply other threads:[~2015-11-17 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 18:20 [Buildroot] [PATCH] liquid-dsp: blacklist CS powerpc toolchains Gustavo Zacarias
2015-11-17 20:19 ` Thomas Petazzoni
2015-11-17 20:24 ` Gustavo Zacarias [this message]
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=564B8D19.9070508@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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