Bug #540
closed"configure: error: unknown endianness" on configure-target-libatomic step
100%
Updated by Dmitry M. almost 10 years ago
- Assignee set to Dmitry M.
It's error related to OS X resources limits:
configure:14401: /private/tmp/ndk-jenkins/build/toolchain/gcc-4.9/./gcc/xgcc -B/private/tmp/ndk-jenkins/build/toolchain/gcc-4.9/./gcc/ -B/tmp/ndk-jenkins/build/toolchain/prefix/mips64el-linux-android/bin/ -B/tmp/ndk-jenkins/build/toolchain/prefix/mips64el-linux-android/lib/ -isystem /tmp/ndk-jenkins/build/toolchain/prefix/mips64el-linux-android/include -isystem /tmp/ndk-jenkins/build/toolchain/prefix/mips64el-linux-android/sys-include -mabi=32 -mips32r2 -c -fexceptions -fpic -O2 -Os -g -DTARGET_POSIX_IO -fno-short-enums -pthread -fno-sync-libcalls conftest.c >&5
xgcc: error trying to exec '/private/tmp/ndk-jenkins/build/toolchain/gcc-4.9/./gcc/cc1': execv: Permission denied
Updated by Dmitry M. almost 10 years ago
Fixed by increasing system resource limits and add checking for them to envsetup.sh
Updated by Dmitry M. almost 10 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100