31.10.2011 13:16, KP Kirchdoerfer пишет: > Am Montag, 31. Oktober 2011, 12:05:01 schrieb KP Kirchdoerfer: >> Am Montag, 31. Oktober 2011, 11:19:38 schrieb Andrew: >>> 31.10.2011 12:05, KP Kirchdoerfer пишет: >>>> Am Samstag, 29. Oktober 2011, 22:37:10 schrieb Andrew: >>>>> Hi all. >>>>> Today I have enough free time to spent it for LEAF toolchain. >>>>> Now I finished very basic rework on it, it looks like now it >>>>> should successfully compile C applications and has working C++ >>>>> compiler w/o c++ libraries (I planned to replace libstdc++ to >>>>> uClibcpp). Now compiler has native architecture - so it'll be no >>>>> pain with cross-compilation in future and it'll be easy to build >>>>> all for new architectures that are binary-incompatible with x86. >>>>> Also it reduces count of ugly tricks in toolchain. >>>> Andrew; >>>> >>>> in my case it failed while trying to build gcc: >>>> >>>> "checking for the correct version of gmp.h... no >>>> configure: error: Building GCC requires GMP 4.2+, MPFR 2.3.1+ and >>>> MPC 0.8.0+" >>>> >>>> kp >>> Do you have libgmp installed in your system? I exclude it from >>> toolchain because it is present in all modern distros, and it was >>> needed earlier only due to cross-compile x86 gcc binaries on x86_64 >>> system. >> I have had installed libgmp, but it does not provide gmp.h, so I >> installed libgmp-dev, libmpfr-dev and libmpc-dev. Seems to be different >> to other distributions. >> >> So it seems to build now... > Not really... > > "make[4]: Leaving directory `/opt/buildtool-next/build/toolchain/gcc- > stage1/i486-pc-linux-uclibc/libgcc' > /opt/buildtool-next/build/toolchain/gcc-stage1/./gcc/xgcc -B/opt/buildtool- > next/build/toolchain/gcc-stage1/./gcc/ -B/opt/buildtool- > next/toolchain/i386/i486-pc-linux-uclibc/bin/ -B/opt/buildtool- > next/toolchain/i386/i486-pc-linux-uclibc/lib/ -isystem /opt/buildtool- > next/toolchain/i386/i486-pc-linux-uclibc/include -isystem /opt/buildtool- > next/toolchain/i386/i486-pc-linux-uclibc/sys-include -g -O2 -O2 -g -O2 > -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wwrite-strings -Wcast-qual > -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem > ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 - > D__GCC_FLOAT_NOT_NEEDED -fno-stack-protector -I. -I. -I../.././gcc - > I/opt/buildtool-next/source/toolchain/gcc-4.6.2/libgcc -I/opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/. -I/opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/../gcc -I/opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/../include -I/opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/config/libbid - > DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o _muldi3.o -MT > _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c /opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/../gcc/libgcc2.c \ > > In file included from /opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/../gcc/libgcc2.c:29:0: > /opt/buildtool- > next/source/toolchain/gcc-4.6.2/libgcc/../gcc/tsystem.h:87:19: fatal error: > stdio.h: No such file or directory > compilation terminated. > make[3]: *** [_muldi3.o] Error 1" > > kp Fixed. uClibc headers were installed into wrong place by my error.
------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev _______________________________________________ leaf-devel mailing list leaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/leaf-devel
