Skip to content
This repository was archived by the owner on Apr 16, 2021. It is now read-only.

Compilation Path Length Issues with Dependant Tools #60

Open
psytribalogical opened this issue Mar 17, 2020 · 3 comments
Open

Compilation Path Length Issues with Dependant Tools #60

psytribalogical opened this issue Mar 17, 2020 · 3 comments

Comments

@psytribalogical
Copy link

We have encountered an issue in using the toolchain included with this package (full thread here), whereby having too many libraries or paths in the compilation will fail with the error "arm-none-eabi-g++: error: CreateProcess: No such file or directory".

We have found that using a newer version of the arm-none-eabi toolset resolves this, and the one currently referenced in the packageindex.json is 2017-q4, which suffers from this issue, whereas updating to the STM32 9.2.1 version resolves this (from this toolchain, within this board package)

Is there a plan to update the dependency at present? (or should this be logged elsewhere?)

An example of a failed and working compilation command are attached:-
ArduinoBLE_FailedCompilationLengthIssue.txt

@facchinm
Copy link
Member

Hi @psytribalogical ,
which WIndows version are you using?
AFAIK the commandline limit was more or less 32000 characters (hence this patch arduino/arduino-builder@ea2e91b).

@psytribalogical
Copy link
Author

This is on Win 10 Pro Version 10.0.18362 Build 18362, and that was the first thing I thought it was too (one of the imposed limits).

Thanks for the pointer to the builder elements on this, and the issue isn't the windows command processor, but the actual exe's internal processing (the newer tool chain works fine with longer commands via the same processor, and the error is being reported from within the arm-none-eabi exe itself).

An example sketch and libraries are attached, along with compilation log, and in this example the inclusion of too many libraries manifests the issue way before the 32k limit (and if we remove the escaping from the build output the same length limitation is seen)

Arduino_1-8-12_BuildOutput.txt
DummyLibraries.zip
SketchExample.zip

@facchinm
Copy link
Member

Updating to avr-gcc 9 could be a good idea but we need to evaluate the impact first on smaller targets (after merging arduino/actions#18 everything should be easier)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants