Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/ffmpeg: fix fenv build failure on ARCv2 with glibc
Date: Wed, 8 Nov 2017 08:38:48 +0100	[thread overview]
Message-ID: <20171108083848.223b0089@windsurf> (raw)
In-Reply-To: <3fa86dc3-5825-96ed-3466-32862ef55088@mind.be>

Hello,

On Wed, 8 Nov 2017 00:24:50 +0100, Arnout Vandecappelle wrote:

>  Doesn't this work?
> 
> config BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS
> 	bool
> 	default y
> 	# blabla why
> 	depends on !BR2_archs38 || !BR2_TOOLCHAIN_USES_GLIBC
> 	# blabla why
> 	depends on !BR2_nios
> 	...
> 
>  I believe we use that construct elsewhere...

Absolutely. Not sure why I over-engineered the thing, your solution
should work perfectly fine.

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

      reply	other threads:[~2017-11-08  7:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 21:11 [Buildroot] [PATCH v2 1/1] package/ffmpeg: fix fenv build failure on ARCv2 with glibc Bernd Kuhls
2017-11-07 21:37 ` Thomas Petazzoni
2017-11-07 23:24   ` Arnout Vandecappelle
2017-11-08  7:38     ` Thomas Petazzoni [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=20171108083848.223b0089@windsurf \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox