Update Two: I removed the --enable-cross...because I'm not interested in building for *another* platform on my device (plus I'm using the NDK standalone toolchain which I believe *is* a cross compiler)...got rid of the -rpath-link and -rpath options and ran 'make -d' successfully.
tarballed the build directory, transferred it to my device and extracted it. Now the problem is that 'make install' fails. I changed a few parameters to try to fix the initial problem (VPATH in Makefile, top_srcdir in config.h) which was that make was looking for files in the directory on my build machine, and now I'm getting the error 'No rule to make target 'install'. Stop.' Feel free to reply with advice. I'm going to continue troubleshooting. On Fri, Aug 30, 2013 at 11:40 AM, Cayce Pollard <[email protected]>wrote: > Update: As per advice from another post, I ran tcc -vvv scm.c. The > output displayed paths that were from my build machine that did not exist > on my device. > > So, I re-ran configure with the following parameters: > > *********************************** > sudo sh /project/tcc-0.9.26/configure --prefix=/usr --enable-cross > --cross-prefix=/project/arm-cc/bin/arm-linux-androideabi- > --sysroot=$SYSROOT --sysincludepaths=/project/arm-cc/sysroot/usr/include > --libpaths=/project/arm-cc/sysroot/usr/lib:/project/arm-cc/arm-linux-androideabi/lib > --extra-cflags=-mfloat-abi=softfp --extra-ldflags='-Wl,-fix-cortex-a8 > -Wl,-rpath-link=-ctro.o ctri1.o > -Wl,-rpath=-signal.h,stio.h,stdlib.h,stdint.h,string.h,strings.h > -Wl,-lsupc++' --cpu=armv7-a --with-libgcc > --crtprefix=/project/arm-cc/sysroot/usr/lib > --elfinterp=/project/arm-cc/bin/arm-linux-androideabi-elfreadelf > *************************************** > > I made the same changes to config.mak and config.h as I did in my original > email and then ran make. A tcc binary was created along with *.o files. I > tarballed the build directory, uploaded it to my device and ran make > install, which failed. > > Running make -n -d install shows that it is trying to copy i386 files and > make win32 directories...which isn't what I want to happen. > > Where am I going wrong? I suspect the 'configure' is incorrect but I'm > not sure. Is there additional documentation for the configure parameters? > > > On Thu, Aug 29, 2013 at 5:16 AM, Cayce Pollard > <[email protected]>wrote: > >> Hello, >> I'm testing the tinycc binary I built for my Android device by attempting >> to build SCM (a lightweight Scheme interpreter) on it. >> >> Running make scmlit (after running configure as per instructions) >> produces the following error: >> >> scm.c:24: error: include file 'signal.h' not found. >> >> Is this a limitation of the Android OS or did I make a mistake in >> building tinycc for Android? >> >> Here's the configure options I used for the build: >> sh /project/tcc-0.9.26/configure --prefix=/usr --enable-cross >> --cross-prefix=/project/arm-cc/bin/arm-linux-androideabi- >> --sysroot=$SYSROOT --sysincludepaths=/project/arm-cc/sysroot/usr/include >> --libpaths=/project/arm-cc/sysroot/usr/lib:/project/arm-cc/arm-linux-androideabi/lib >> --extra-cflags=-mfloat-abi=softfp --extra-ldflags='-Wl,-fix-cortex-a8 >> -Wl,-rpath-link=/project/arm-cc/sysroot/usr/lib -Wl,-lsupc++' --cpu=armv7-a >> --with-libgcc --crtprefix=/project/arm-cc/sysroot/usr/lib >> --elfinterp=/project/arm-cc/bin/arm-linux-androideabi-readelf >> --cc=/project/arm-cc/bin/arm-linux-androideabi-gcc-4.7 >> >> In config.h I made this change (in parens): >> #define TCC_ARM_VERSION (*7)* >> * >> * >> And in config.mak I made this change (again in parens): >> CC=/project/arm-cc/bin/arm-linux-androideabi-gcc-(*4.7)* >> * >> * >> >> >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
