Bug #900
closed
standalone arm-linux-androideabi-4.9 fails to compile: cannot find -lcrystax
Added by Xiao Bao C. almost 10 years ago.
Updated over 9 years ago.
Android version:
4.2 (android-17)
Description
I made a standalone toolchain with the @make-standalone-toolchain.sh@ script:
$CRYSTAX_NDK/build/tools/make-standalone-toolchain.sh --verbose --toolchain=arm-linux-androideabi-4.9 --arch=arm --abis=armeabi-v7a --install-dir=$STANDALONE --platform=android-17
Attempting to do a test compilation fails:
echo "int main(){}" | ${STANDALONE}/bin/arm-linux-androideabi-gcc -x c -o tst -
$STANDALONE/bin/../lib/gcc/arm-linux-androideabi/4.9/../../../../arm-linux-androideabi/bin/ld: error: cannot find -lcrystax
collect2: error: ld returned 1 exit status
OS: Linux Mint Rebecca (17.1)
Crystax version: 10.1.0
- Assignee set to Dmitry M.
- Priority changed from Normal to High
Thanks for looking into it. The workaround I'm using:
export LDFLAGS=-L${STANDALONE}/arm-linux-androideabi/lib/armv7-a
The only issue is that the thumb version will never be used, but that shouldn't cause any runtime issues
Xiao Bao Clark wrote:
The only issue is that the thumb version will never be used, but that shouldn't cause any runtime issues
If you need thumb version, you can specify:
export LDFLAGS=-L${STANDALONE}/arm-linux-androideabi/lib/armv7-a/thumb
Anyway, I confirm the bug is really present - gcc for some reason stopped including that library path into default linker search path list. The most interesting thing is that all our standalone tests passed successfully, but your specific case doesn't work.
We're working on it and will include the fix to the next release. In the meantime, please use workaround with LDFLAGS.
- Status changed from Open to In Progress
- Status changed from In Progress to Completed
- % Done changed from 0 to 100
- Target version set to 10.2.0
Also available in: Atom
PDF