Skip to content
This repository has been archived by the owner on Feb 5, 2020. It is now read-only.

[GCC_ARM] Do not compile on windows #17

Closed
pan- opened this issue Jul 25, 2018 · 3 comments
Closed

[GCC_ARM] Do not compile on windows #17

pan- opened this issue Jul 25, 2018 · 3 comments
Labels
external-dependency Waiting for external fix

Comments

@pan-
Copy link

pan- commented Jul 25, 2018

On windows, it is not possible to compile with the official version of GCC ARM 6. The compiler crash with as it cannot accepts more than 32K of characters on the command line.

@theotherjimmy

@theotherjimmy
Copy link

@pan- See ARMmbed/mbed-os#7583

@pan-
Copy link
Author

pan- commented Jul 26, 2018

@theotherjimmy That is partially related to my issue.
I do compile with mbed cli and I can see the response file on the command line (@<response file name>). However it seems that the content of the response file is passed as command argument to a program invoked by GCC.

It fails with the error ToolException: arm-none-eabi-gcc: error: CreateProcess: No such file or directory

If I do remove manually some includes path out of 415 includes path present in the response file so the total command line is bellow 32K then if I manually launch the same GCC command; it works.

@MarceloSalazar
Copy link
Contributor

This is a known Windows path problem - ARMmbed/mbed-os#7129
Waiting for a fix in the Mbed OS tools.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
external-dependency Waiting for external fix
Projects
None yet
Development

No branches or pull requests

3 participants