Can't start process ... \gcc\bin\ld

Follow

Rooster250F

• November 21, 2009 23:44

Hi,

I am just getting started learning CrossWorks for ARM and am having a little trouble.

I am running the evaluation version and have written a simple program to start learning how to compile/link etc.

void main(void)
{
  int val1;

    while(1)
      {
          val1++;
       }
}

The program compiles fine but generates the following error when linking:

Generating linker script
Linking test_23.elf
Can't start process C:/Program Files/Rowley Associates Limited/CrossWorks for ARM 2.0/gcc/bin/ld
Build failed

 

The file ld.exe does exist in the .../gcc/bin directory so I'm not sure why it can't start it.

I would be very grateful to anyone that can help get me over this hurdle.

Thanks

0

• 

  Jon Elliott

  • November 23, 2009 11:15

  Do you have permission to execute the ld.exe file?

  0

  Comment actions Permalink
• 

  Rooster250F

  • November 25, 2009 12:34

  Yes, I appear to have permission to run ld.exe.

  I am able to run it from a DOS window, I don't know what switches to use but at least it tries to run.

  Could it be something in the 'path' setup?

  0

  Comment actions Permalink
• 

  Jon Elliott

  • November 26, 2009 09:44

  Do you have a file "C:/Program" by any chance? We've seen that cause problems in the past.

  
  I'm a bit puzzled why the compiler is working but the linker isn't, just to verify that this is still the case can you rebuild the project (click Build > Rebuild project) and let me know the complete output.

   

   

  0

  Comment actions Permalink
• 

  Rooster250F

  • December 02, 2009 01:10

  I ended up uninstalling and reinstalling Crossworks and now it works fine???

  I only have 13 days left on my evaluation license so I better get busy evaluating!

  Thanks for your help Jon.

   

  0

  Comment actions Permalink
• 

  Travis Fields

  • July 06, 2011 16:19

  Just thought I would drop my two cents in.  I had this problem with CC1.exe, and found that it WAS having this random file C:\program.  After deleting it everything worked fine.

  0

  Comment actions Permalink

Please sign in to leave a comment.