Hi,

I hope this it is ok to post this question to this forum - I think the
sparkfun one may be more appropriate but it appears to be borked at the
moment.

I'm having a few problems getting Eclipse to compile for an ARM target
cleanly.  My setup is based on J Lynch's tutorial - I'm using an Olimex
ARM-USB-OCD and an atmel AT91SAM7S256 evaluation board.

I have put together the "demo_at91sam7_blink_flash" project as per the
tutorial.  My problem comes when I try to build it.  Clicking
"Project->Buld All" result in the build process freezing at around 16%.
I have added an extra "-v" to the CFLAGS section of the makefile to try
and see what is going on; below are the last few entries of the console
window:


 C:/Program Files/yagarto/libexec/gcc/arm-elf/4.1.1/cc1.exe -quiet -v
-I./ -iprefix c:\program files\yagarto\bin\../lib/gcc/arm-elf/4.1.1/
-D__USES_INITFINI__ timersetup.c -quiet -dumpbase timersetup.c -auxbase
timersetup -g -O0 -version -fno-common -o
C:\DOCUME~1\ben\LOCALS~1\Temp/ccqIbaaa.s
ignoring nonexistent directory "C:/Program
Files/yagarto/arm-elf/sys-include"
ignoring nonexistent directory "./"
#include "..." search starts here:
#include <...> search starts here:
 c:\program files\yagarto\bin\../lib/gcc/arm-elf/4.1.1/include
 C:/Program Files/yagarto/lib/gcc/arm-elf/4.1.1/include
 C:/Program Files/yagarto/arm-elf/include
End of search list.
GNU C version 4.1.1 (arm-elf)
  compiled by GNU C version 3.4.5 (mingw special).
GGC heuristics: --param ggc-min-expand=100 --param
ggc-min-heapsize=131072
Compiler executable checksum: 9b367e19cd34814df5c96e09493c472e
 c:/program
files/yagarto/bin/../lib/gcc/arm-elf/4.1.1/../../../../arm-elf/bin/as.ex 
e
-o timersetup.o C:\DOCUME~1\ben\LOCALS~1\Temp/ccqIbaaa.s


I'm using all the latest versions from the Yagarto site.  The strangest
thing is that sometimes the build succeeds.  When this is the case, I am
able to do the next steps in the tutorial (the "Project->Build Make
Targert" part) and the compiled code sucessfully flashes to the
processor and runs.

In the case when the compile fails I find that the only way to kill the
build process is to stop (via task manager) one or all of the following:
  as.exe
  starter.exe



Here is my path variable:


%systemroot%\system32;%systemroot%;%systemroot%\system32\wbem;c:\program
files\wave systems corp\dell preboot manager\access
client\v5\;C:\Program Files\MATLAB\R2007a\bin;C:\Program
Files\MATLAB\R2007a\bin\win32;c:\program
files\matlab\r2006b\bin;c:\program
files\matlab\r2006b\bin\win32;c:\program files\microsoft sql
server\90\tools\binn\;c:\program files\common
files\gtk\2.0\bin;c:\program files\pico technology\pico
%systemroot%\system32;%systemroot%;%systemroot%\system32\wbem;c:\program
files\wave systems corp\dell preboot manager\access
client\v5\;C:\Program Files\MATLAB\R2007a\bin;C:\Program
Files\MATLAB\R2007a\bin\win32;c:\program
files\matlab\r2006b\bin;c:\program
files\matlab\r2006b\bin\win32;c:\program files\microsoft sql
server\90\tools\binn\;c:\program files\common
files\gtk\2.0\bin;c:\program files\pico technology\pico full\;C:\Program
Files\openocd-2007re141\bin;C:\Program
Files\openocd-2007re141\utils\bin;C:\Program Files\yagarto\bin



A few observations which may / may not be relevant:

1. The paths displayed in the console window have a mixture of / and \
in them.
2. "Project -> Properties -> C/C++ Make Project -> Discovery Options ->
Compiler invocation command" is currently set to gcc - should this be
arm-elf-gcc?



Thanks in advance for any help,

Ben Smither

I've done a bit more digging and it seams that the following command,
when run in the project directory, is unstable:

arm-elf-gcc -I./ -c -fno-common -O0 -g main.c

Sometimes it will run and make main.o etc, sometime it will just hang.
Could this be something specific to my laptop - it has an intel core 2
duo processor?

Thanks

Ben