From: Peter B. <pmv...@on...> - 2006-06-25 10:42:31
|
Hello all, is there a gumstix cross-compiler installation manual, guide or something like this which is suited for absolute beginners and linux novices? I have read the FAQ list and some other information on the gumstix site but still have problems with the cross compiler. Invoking the compiler within a terminal just gives "Command not found", even if the full path is specified. Adding the path of the compiler and making an alias does not solve the problem. Maybe there is a problem with my installation. Beneath lots of warnings (ok, I know warnings are no error messages) there were some error (?) messages like "command not found" or "file does not exist". Nevertheless, the installing/compiling process ended without error message. Is there a message/sign which indicates a correct installation? Thanks in advance Peter |
From: Dave H. <dhy...@gm...> - 2006-06-25 16:32:16
|
HI Peter, > is there a gumstix cross-compiler installation manual, guide or > something like this which is suited for absolute beginners and linux > novices? I have read the FAQ list and some other information on the > gumstix site but still have problems with the cross compiler. Invoking > the compiler within a terminal just gives "Command not found", even if > the full path is specified. Adding the path of the compiler and making > an alias does not solve the problem. Maybe there is a problem with my > installation. Beneath lots of warnings (ok, I know warnings are no error > messages) there were some error (?) messages like "command not found" or > "file does not exist". Nevertheless, the installing/compiling process > ended without error message. Is there a message/sign which indicates a > correct installation? So, have you downloaded the source from SVN and done this from within the gumstix-buildroot directory? make defconfig make These are the two steps that create the cross compiler (and lots of other stuff too). When you've done that and you do ls build_arm_nofpu/staging_dir/bin/ you should see something like this: arm-linux-addr2line@ arm-linux-objdump@ arm-linux-uclibc-gcc@ arm-linux-uclibc-strip* arm-linux-ar@ arm-linux-ranlib@ arm-linux-uclibc-gcc-3.4.5* dlist_test* arm-linux-as@ arm-linux-readelf@ arm-linux-uclibc-gccbug* get_bus_devices_list* arm-linux-c++filt@ arm-linux-size@ arm-linux-uclibc-gcov* get_class_dev* arm-linux-cc@ arm-linux-sstrip@ arm-linux-uclibc-ld* get_classdev_parent* arm-linux-cpp@ arm-linux-strings@ arm-linux-uclibc-nm* get_device* arm-linux-gcc@ arm-linux-strip@ arm-linux-uclibc-objcopy* get_driver* arm-linux-gcc-3.4.5@ arm-linux-uclibc-addr2line* arm-linux-uclibc-objdump* makedevs* arm-linux-gccbug@ arm-linux-uclibc-ar* arm-linux-uclibc-ranlib* mkimage* arm-linux-gcov@ arm-linux-uclibc-as* arm-linux-uclibc-readelf* systool* arm-linux-ld@ arm-linux-uclibc-c++filt* arm-linux-uclibc-size* testlibsysfs* arm-linux-nm@ arm-linux-uclibc-cc@ arm-linux-uclibc-sstrip* write_attr* arm-linux-objcopy@ arm-linux-uclibc-cpp* arm-linux-uclibc-strings* That means that yo now have a cross compiler. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |