>Just a suggestion: export a path to the OSELAS toolchain that is in /opt and >use >that, rather than 4.3.2
>Ok, I'll be honest, I have no idea what that means. I did some googling to try and find out but I didn't find anything I understood. Is there a gcc compiler built into my >toolchain that I use to compile C code? Or do I have to find the path associated with /opt/my_toolchain and include it in some sort of makefile? I figured it out. The first file I was trying to compile with wasn't an actual compiler. It was located elsewhere. I'll post the path in case anybody reads this for help. /opt/OSELAS.Toolchain-2011.11.0/arm-v4t-linux-gnueabi/gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/bin/arm-v4t-linux-gnueabi-gcc I made a link to this file in / so it is easily accessible when I compile. ln -s (path above) /arm-gcc so to compile, simply call form anywhere /arm-gcc -o file filename.c
