[cc] arm-none-eabi-gcc: error: CreateProcess: No such file or directory

Asked by Herman Botha

Try to execute:
arm-none-eabi-gcc -mcpu=cortex-m0 -mthumb -Wall -ffunction-sections -g -O0 -c -IC:\CooCox\CoIDE\workspace C:\CooCox\CoIDE\workspace\main.c C:\CooCox\CoIDE\workspace\example\BlinkExp.c

or even:
 arm-none-eabi-gcc main.c

Response is always:
 [cc] arm-none-eabi-gcc: error: CreateProcess: No such file or directory

Downloaded various versions of arm-none-eabi-gcc, they all give the same error, what could the cause be?

Question information

Language:
English Edit question
Status:
Answered
For:
GNU Arm Embedded Toolchain Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Joey Ye (jinyun-ye) said :
#1

This is a coide problem, suggest asking in coocox forum. It could be path
setting problem.
On Apr 20, 2013 11:21 PM, "Herman Botha" <
<email address hidden>> wrote:

> New question #227124 on GCC ARM Embedded:
> https://answers.launchpad.net/gcc-arm-embedded/+question/227124
>
> Try to execute:
> arm-none-eabi-gcc -mcpu=cortex-m0 -mthumb -Wall -ffunction-sections -g -O0
> -c -IC:\CooCox\CoIDE\workspace C:\CooCox\CoIDE\workspace\main.c
> C:\CooCox\CoIDE\workspace\example\BlinkExp.c
>
> or even:
> arm-none-eabi-gcc main.c
>
> Response is always:
> [cc] arm-none-eabi-gcc: error: CreateProcess: No such file or directory
>
> Downloaded various versions of arm-none-eabi-gcc, they all give the same
> error, what could the cause be?
>
> --
> You received this question notification because you are an answer
> contact for GCC ARM Embedded.
>

Revision history for this message
Günter Fuchs (gunter-fuchs) said :
#2

Try first arm-none-eabi-gcc --version.
Then run arm-none-eabi-gcc -v main.c. That shows you what processes gcc wants to create. Maybe its output helps you to get further.

Revision history for this message
Joey Ye (jinyun-ye) said :
#3

Herman,

When this happens, usually it is environment setting up problem. Suggest to check followings:
1. Is there other GCC toolchain installed?
2. Is there other GCC toolchain in the path? If yes, remove them from path
3. Is GCC_EXEC_PREFIX environment set? If set, just unset it.

Hopefully this is helpful for you to identify the problem.

Thanks - Joey

Can you help with this problem?

Provide an answer of your own, or ask Herman Botha for more information if necessary.

To post a message you must log in.