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: Tue, 7 Nov 2017 22:37:52 +0100 [thread overview]
Message-ID: <20171107223752.3844357c@windsurf> (raw)
In-Reply-To: <20171107211149.17617-1-bernd.kuhls@t-online.de>
Hello,
On Tue, 7 Nov 2017 22:11:49 +0100, Bernd Kuhls wrote:
> https://git.buildroot.net/buildroot/commit/toolchain?id=0633eb58a2912328508a76f8fe9875a0d113a880
> added glibc support for ARCv2 which lacks fenv.h.
>
> Fixes
> http://autobuild.buildroot.net/results/aec/aec300d7d4472421398a24202d6871c965bd1be5/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
Thanks!
Reviewed-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> - # fenv.h lacks FE_INVALID, FE_OVERFLOW & FE_UNDERFLOW on nios2
> + # fenv.h lacks FE_INVALID, FE_OVERFLOW & FE_UNDERFLOW on archs38
> + # in combination with glibc and nios2
> # No support for ARMv7-M in the ARM assembly logic
> # Microblaze build affected by gcc PR71124 (infinite loop)
> # m68k coldfire causes a build failure, because the check for
> @@ -9,7 +10,9 @@ config BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS
> # not. See https://patchwork.ozlabs.org/patch/756664/ and
> # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68467 for more
> # details.
> - default y if !BR2_nios2 && !BR2_ARM_CPU_ARMV7M && !BR2_microblaze && !BR2_m68k_cf
> + default y if !(BR2_archs38 && BR2_TOOLCHAIN_USES_GLIBC) && \
> + !BR2_nios2 && !BR2_ARM_CPU_ARMV7M && \
> + !BR2_microblaze && !BR2_m68k_cf
We don't want to fix that now, but this is getting unreadable. Perhaps
we could improve that by doing this:
config BR2_PACKAGE_FFMPEG_ARCH_BROKEN
bool
# blabla why
default y if BR2_archs38 && BR2_TOOLCHAIN_USES_GLIBC
# blabla why
default y if BR2_nios2
# ...
default y if BR2_ARM_CPU_ARMV7M
# ...
default y if BR2_microblaze
# blabla why
default y if BR2_m68k_cf
config BR2_PACKAGE_FFMPEG_ARCH_SUPPORTS
bool
default y if !BR2_PACKAGE_FFMPEG_ARCH_BROKEN
It's probably more readable :)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-11-07 21:37 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 [this message]
2017-11-07 23:24 ` Arnout Vandecappelle
2017-11-08 7:38 ` 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=20171107223752.3844357c@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 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.