Hello, i am having problems getting the GNU tools to run under Keil. It is not the well-known problem of the CGWIN path or the arm-uclibc- prefix. Compiler and assembler do their work, but when the linker gets engaged, i get a message collect2: cannot find 'ld' collect2.exe itself, when started from a dos box, gives a "cannot find ld". Even remaining arm-uclibc-ld.exe to ld.exe and beyond that copying it into the c:\Cygnus\arm-tools\lib\gcc-lib\arm-thumb-elf\e.3.1 dir side by side to that collect2.exe did not help. I have worked some hours through the GNU docs, that i have here and have tried some solutions, eg setting an environment variable COLLECT_NO_DEMANGLE did not help. To be honest, i am "a bit" fighting in the fog with the gnu tools and just at the very beginning of some understanding. Though i like them the more i learn about it.. I do have various gnu tollsets on my PC, but don*t see any cross-effects and even hiding/renaming their dirs did not help. (Win32 / CrossStudio Eval / CodeSourcery GNU Toolchain) BTW: The "links" in the c:\Cygnus folder do look quite strange, seemingly being no standard windows links. Checking the properties of the links to executables reveals empty fields for targets and working directories. Looking at their content comes up with e.g. ../../bin/arm-uclibc-gcc.ex C:\cygwin\arm-tools\bin\arm-uclibc-gcc.exe though the dir is clearly not c:\cygwin bit c:\Cygnus. Maybe a specialty from the ?company? Cygwin? for their product ?cygnus? I have not fiddled around with some homemade project. This happens with the unmodified hello project from \ARM\GNU\EXAMPLES\hello But to cut the story short: What can i do to get it to work? (Using Keil uVision 3 v3.21 ARM evaluation) Finally a big thanks to whom deserves: The Keil CD is so full of useful information, datasheets and an extremely generous handling of the evaluation policy for the IDE and tools, that the Keil people deserve a strong applause. Useless to translate my feeling to english ("mir blieb die Spucke weg"). Though some details could be worked out a bit (for beginners?), mostly regarding the help (C51/ARM mangling) and some tricks, eg. the possibility to write an ini file for the debugger/simulator and what to put into that. I have spent some time in manually opening the memory range in the simulator before i found that. Great work! Greetings Eric PS: Probably someone will ask, why i don't simply use the Keil toolset. I would like to do so, and will do for pure assembly projects... but for C projects the Keil tools won't work in this case, because i am (mis)using an oldtimer ARM from around 1995, a model 2 or 2A and it doesn't know anything about CPSR and SPSR registers or BX commands. To answer the next question, why i am using that oldie: 1) because i have it 2) i like the challenge 3) there is a lot of hardware on that board, that can not be found on any development board. (ISDN equipment) I have been tempted of "cracking" into the keil libraries and exchangig those little beasty parts in the code, but it would probably take some days to find the right places and it might be a case where Keil would not be amused of.. retro-cracking their software ... ;)))