How can I test if gcc-avr is working? Can I compile in a terminal to see errors in detail?
(I am still trying to solve how to run arduino on my Acer Aspire One and it seems to me to be only a problem of the compiler of which might have a non-working version. Everything is working except for that I am getting an .elf file in stead of the needed .hex)
Can I compile in a terminal to see errors in detail?
Yeah. The tools are in /hardware/tools/bin, and you can use a command like:
/Downloads/arduino-0013/hardware/tools/avr/bin/avr-gcc -c -g -Os -w -ffunction-sections -fdata-sections -mmcu=atmega168 -DF_CPU=16000000L -I/Downloads/arduino-0013/hardware/cores/arduino foo.c -o foo.o
(Subject to differences in operating system, of course. The key pieces are the compiler location and the -I switch go get the right include files...)
If I try to compile Blink.pde I get this funny message:
avr-gcc: Blink.pde: linker input file unused because linking not done
Now the question: How do I get the linking done?
I don't see any output from the compile process so I don't know if anything happened.
If I try to compile Blink.pde I get this funny message:
You can't compile the PDE-files directly. The Arduino IDE does some preprocessing of these files, which includes adding prototypes, #includes and - most importantly - a main-function. So to be able to compile a pde-file you need to add these things manually.
You can also look inside the applet-folder in the sketch-folder, where you can find the pre-processed cpp-file generated by the IDE.