search

dongxie / android-cmake

Automatically exported from code.google.com/p/android-cmake
0 stars 0 forks source link

make-standalone-toolchain.sh #7

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Using cygwin terminal, I run the make-standalone-toolchain script:

This is tha command I write:
$ sh make-standalone-toolchain.sh --ndk-dir=$NDK --platform=android-9 \ 
--install-dir=$ANDROID_SDK/android-toolchain

This is the output for the script:
Auto-config: --toolchain=arm-linux-androideabi-4.4.3
Copying prebuilt binaries...
Copying sysroot headers and libraries...
Copying libstdc++ headers and libraries...
mkdir: cannot create directory 
`/tmp/ndk-ayesh/tmp/build-5788/standalone/arm-linux-androideabi-4.4.3/arm-linux-
androideabi': Permission denied
ERROR: Cannot copy to directory: 
/tmp/ndk-ayesh/tmp/build-5788/standalone/arm-linux-androideabi-4.4.3/arm-linux-a
ndroideabi/include/c++/4.4.3

What version of the product are you using? On what operating system?
windows-7-x64, ndk-r7b, and cygwin.

Additional information:
I'm using cygwin on windows-7-x64, and the most important question is, am I 
waiting my time and should give up on windows with cygwin and use linux instead?

Original issue reported on code.google.com by ayeshqum...@gmail.com on 27 May 2012 at 1:43

GoogleCodeExporter commented 9 years ago 
OK, it seems does not support sudo, It works on windows Administrative users 
permissions, so running cygwin as an administrator solves the problem.

Original comment by ayeshqum...@gmail.com on 27 May 2012 at 3:19

GoogleCodeExporter commented 9 years ago 
echo "Create new NDK toolchain..."
#if this line cast the error:mkdir: cannot create directory `/tmp/ndk-...;
#you must add this line "none /cygdrive cygdrive binary,user,noacl,posix=0 0 0" 
to /etc/fstab file
$NDK_ROOT/build/tools/make-standalone-toolchain.sh --platform=$PLATFORM 
--install-dir=$TOP_FFMPEG_DIR/android-toolchain

Original comment by Jibing.Z...@gmail.com on 31 May 2012 at 9:00

GoogleCodeExporter commented 9 years ago 
it's because wherever you're running the script is read-only (check ls -l).

in the worst case chmod 777 -R the whole ndk dir, it will work.

Original comment by esx...@gmail.com on 27 Feb 2013 at 10:07