From: Hamilton, F. C. W. A. & I. D. C. 4. <fra...@na...> - 2007-11-08 20:29:14
|
I tried what you suggested, but now I'm getting a different error. Now = ./configure encounters an error and aborts saying "C Compiler cannot = create executables". The command I'm using is: "CC=3Darm-linux-gcc = ./configure --host=3Darm-linux", but I get the same error when I use = "CC=3Darm-linux-uclibcgnueabi-gcc ./configure etc". =20 And some of the output from the config.log file is below. One strange = thing is that even though the PATH variable in the terminal includes the = path to the arm-linux stuff in the buildroot, it doesn't always show up = in the config.log file. I've only been using Linux for about a month so = I'm still really new to this. Any help would be greatly appreciated. =20 Thanks, Franklin Hamilton =20 config.log =20 hostname =3D uaslab-desktopU uname -m =3D i686 uname -r =3D 2.6.20-16-generic uname -s =3D Linux uname -v =3D #2 SMP Sun Sep 23 19:50:39 UTC 2007 /usr/bin/uname -p =3D unknown /bin/uname -X =3D unknown /bin/arch =3D i686 /usr/bin/arch -k =3D unknown /usr/convex/getsysinfo =3D unknown hostinfo =3D unknown /bin/machine =3D unknown /usr/bin/oslevel =3D unknown /bin/universe =3D unknown PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/sbin PATH: /usr/bin PATH: /sbin PATH: /bin PATH: /usr/X11R6/bin =20 ## ----------- ## ## Core tests. ## ## ----------- ## configure:1541: checking build system type configure:1559: result: i686-pc-linux-gnu configure:1567: checking host system type configure:1581: result: arm-unknown-linux-gnu configure:1589: checking target system type configure:1603: result: arm-unknown-linux-gnu configure:1634: checking for a BSD-compatible install configure:1689: result: /usr/bin/install -c configure:1700: checking whether build environment is sane configure:1743: result: yes configure:1808: checking for gawk configure:1837: result: no configure:1808: checking for mawk configure:1824: found /usr/bin/mawk configure:1834: result: mawk configure:1844: checking whether make sets $(MAKE) configure:1864: result: yes configure:1940: checking for arm-linux-strip configure:1969: result: no configure:1978: checking for strip configure:1994: found /usr/bin/strip configure:2005: result: strip configure:2060: checking for style of include used by make configure:2088: result: GNU configure:2121: checking for arm-linux-gcc configure:2147: result: arm-linux-gcc configure:2429: checking for C compiler version configure:2432: arm-linux-gcc --version </dev/null >&5 ./configure: line 2433: arm-linux-gcc: command not found configure:2435: $? =3D 127 configure:2437: arm-linux-gcc -v </dev/null >&5 ./configure: line 2438: arm-linux-gcc: command not found configure:2440: $? =3D 127 configure:2442: arm-linux-gcc -V </dev/null >&5 ./configure: line 2443: arm-linux-gcc: command not found configure:2445: $? =3D 127 configure:2468: checking for C compiler default output file name configure:2471: arm-linux-gcc conftest.c >&5 ./configure: line 2472: arm-linux-gcc: command not found configure:2474: $? =3D 127 configure: failed program was: | /* confdefs.h. */ ________________________________ From: gum...@li... on behalf of Dave = Hylands Sent: Tue 11/6/2007 2:58 PM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Problems cross-compiling software = (gphoto2)onto gumstix Hi Franklin, > ./configure --host=3Darm-linux > --prefix=3D/home/uaslab/gumstix-buildroot/build_arm_nofpu/root > make && make install > > And I do this for the gphoto2 software and the different libraries I = think > it needs to run. Then I go to the buildroot directory, type make, = then > follow the instructions to copy the buildroot filesystem over to the > gumstix. It looks like everything goes off without a hitch, but when = I log > into my gumstix and try to run the command "gphoto2" to start up the > program, I get a weird error: > > /bin/gphoto2: 1: Syntax Error "(" unexpected This normally means that the /bin/gphoto2 is actually an i386 binary instead of an arm binary, which means that the arm cross compiler wasn't used during the build. There are many components to the compiler, so I can't give a complete answer, but normally you have to do something like: CC=3Darm-linux-uclibcgnueabi-gcc ./configure rest-of-args which assumes that arm-linux-uclibcgnueabi-gcc is in your PATH. You may also need to setup AR, LD, etc. It really depends on the package. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ -------------------------------------------------------------------------= This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |