[x264-devel] Compile errors using Android NDK r5c
辛柏成
xinbc2010 at gmail.com
Wed Oct 19 07:19:01 CEST 2011
Hi,everyone:
I've tried to build x264 with Google's NDK r4b in cygwin for Android
platform. But an internal error: segmentation fault came up when compiling
the arm-neon source file.
So I'm trying to compile the x264 source code with Google's NDK r5c.
But, to my surprise, there are so many errors when I compile the C source
file while I could pass the build without enable arm-neon using NDK r4b.
Could anyone help me out? Thanks.
The compile errors:
garethxin at GARETHXIN-PC ~/hello-jni
$ ndk-build
Gdbserver : [arm-linux-androideabi-4.4.3] libs/armeabi/gdbserver
Gdbsetup : libs/armeabi/gdb.setup
Compile thumb : hello-jni <= hello-jni.c
Compile thumb : hello-jni <= common.c
In file included from
C:/cygwin/home/garethxin/android-ndk-r5c/platforms/android
-9/arch-arm/usr/include/sys/types.h:34,
from
C:/cygwin/home/garethxin/android-ndk-r5c/platforms/android
-9/arch-arm/usr/include/stdio.h:55,
from
C:/cygwin/home/garethxin/hello-jni/jni/common/osdep.h:32,
from
C:/cygwin/home/garethxin/hello-jni/jni/common/common.h:86,
from
C:/cygwin/home/garethxin/hello-jni/jni/common/common.c:27:
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:33: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'int64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:34: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'uint64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:43: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'int_least64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:44: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'uint_least64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:56: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'int_fast64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:57: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'uint_fast64_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:64: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'intmax_t'
C:/cygwin/home/garethxin/hello-jni/jni/extras/stdint.h:65: error: expected
'=',
',', ';', 'asm' or '__attribute__' before 'uintmax_t'
In file included from
C:/cygwin/home/garethxin/hello-jni/jni/common/common.h:172
,
from
C:/cygwin/home/garethxin/hello-jni/jni/common/common.c:27:
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:51: error:
expected sp
ecifier-qualifier-list before 'intptr_t'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h: In function
'bs_init'
:
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:86: error:
'intptr_t'
undeclared (first use in this function)
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:86: error: (Each
undec
lared identifier is reported only once
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:86: error: for
each fu
nction it appears in.)
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:86: error:
expected ')
' before 'p_data'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:89: error: 'bs_t'
has
no member named 'i_left'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:90: error: 'bs_t'
has
no member named 'cur_bits'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:91: error: 'bs_t'
has
no member named 'cur_bits'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h: In function
'bs_pos':
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:95: error: 'bs_t'
has
no member named 'i_left'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h: In function
'bs_flush
':
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:101: error: 'bs_t'
has
no member named 'cur_bits'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:101: error: 'bs_t'
has
no member named 'i_left'
C:/cygwin/home/garethxin/hello-jni/jni/common/bitstream.h:102: error: 'bs_t'
has
no member named 'i_left'
Baicheng Xin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20111019/005ff6bf/attachment.html>
More information about the x264-devel
mailing list