[OE-core] [PATCH] x264: Update to latest on stable branch

[Burton, Ross]

On 8 November 2016 at 05:23, Khem Raj <raj.khem at gmail.com> wrote:

> - Switch URI to use github mirror for reliabality
> - Disable openCL code, its not used
> - TEXTRELs are fixed, therefore dont skip QA check
>
> Signed-off-by: Khem Raj <raj.khem at gmail.com>
>

Breaking here for x86-64.

configure output:

DEBUG: Executing shell function do_configure
Unknown option --disable-static, ignored
Found x86_64-poky-linux-gcc (GCC) 6.2.0
Minimum version is yasm-1.2.0
If you really want to compile without asm, configure with --disable-asm.
WARNING: exit code 1 from a shell command.

config.log:

x264 configure script
Command line options: "--prefix=/usr" "--host=x86_64-poky-linux"
"--libdir=/usr/lib" "--cross-prefix=x86_64-poky-linux-"
"--sysroot=/data/poky-master/tmp-glibc/sysroots/intel-corei7-64"
"--enable-shared" "--enable-static" "--disable-lavf" "--disable-swscale"
"--disable-opencl" "--enable-pic" "--disable-static"

checking whether x86_64-poky-linux-gcc  -m64 -march=corei7 -mtune=corei7
-mfpmath=sse -msse4.2
--sysroot=/data/poky-master/tmp-glibc/sysroots/intel-corei7-64 works... yes
checking whether x86_64-poky-linux-gcc  -m64 -march=corei7 -mtune=corei7
-mfpmath=sse -msse4.2
--sysroot=/data/poky-master/tmp-glibc/sysroots/intel-corei7-64 supports
for( int i = 0; i < 9; i++ ); with -std=gnu99... yes
checking for -mpreferred-stack-boundary=5... yes
checking whether x86_64-poky-linux-gcc supports vpmovzxwd ymm0, xmm0... no
Failed commandline was:
--------------------------------------------------
x86_64-poky-linux-gcc conftest.asm  -I. -I$(SRCPATH) -DARCH_X86_64=1
-I$(SRCPATH)/common/x86/ -f elf64  -o conftest.o
x86_64-poky-linux-gcc: error: elf64: No such file or directory
x86_64-poky-linux-gcc: error: unrecognized command line option '-f'
--------------------------------------------------
Failed program was:
--------------------------------------------------
vpmovzxwd ymm0, xmm0
--------------------------------------------------

Ah, looks like the configure is respecting the AS environment variable that
we set to 'as' in bitbake.conf, but it really actually wants yasm.  I added
AS[unexport] = 1 to the recipe and it appears to work now for me.  Can you
verify that it still works on the architectures you care about?

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20161108/8aa55080/attachment-0002.html>