From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Revert "package/x265: bump version to 2.1"
Date: Sun, 6 Nov 2016 22:52:24 +0100 [thread overview]
Message-ID: <20161106225224.5283ba8e@free-electrons.com> (raw)
In-Reply-To: <20161106161924.9791-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 6 Nov 2016 17:19:24 +0100, Bernd Kuhls wrote:
> This reverts commit 1ba7b6a4f12977aec994c4f38d5be38cfdb27846.
>
> Adding -DCROSS_COMPILE_ARM=ON to _CONF_OPTS will not fix the build:
>
> /home/buildroot/br2/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/include/gnu/stubs.h:7:29:
> fatal error: gnu/stubs-soft.h: No such file or directory
>
> because cross-compiling x265 is only supported for soft-float abi:
> https://bitbucket.org/multicoreware/x265/src/583fc74fc0a29f330187dbd78151c30a3e03d5a7/source/CMakeLists.txt?at=default#CMakeLists.txt-211
>
> Fixes
> http://autobuild.buildroot.net/results/6ec/6ec75cc176e05bfc6287dc54fa1a53e0ffc0521d/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
I've applied to master as a temporary measure. But the real fix is to
report the problem upstream, and to tell them to stop hard-cording silly
CFLAGS in their CMakeLists.txt. The only one that potentially makes
sense is -mfpu=neon when NEON support is enabled. All the other ones
should be removed.
Could you work on this with upstream?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-06 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 16:19 [Buildroot] [PATCH 1/1] Revert "package/x265: bump version to 2.1" Bernd Kuhls
2016-11-06 21:52 ` 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=20161106225224.5283ba8e@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox