Hello,

Following previous request, I have by dichotomie try to find a point of failure:

1. Marlin 2.1 OK
2. Marlin 2.1.2 ok
3. Marlin 2.1.2.3 ok
4. Marlin 2.1.2.5 ok
5. 📝 Update HAL documentation, README 24/11/2024 07:00:32 ok
6. marlin 30/11/2024 21:25:55 📌 Update, pin LPC PIO framework (📌 Update, pin LPC PIO framework #27554) ko

For the moment, I don't find reason, look CC is c compiler ?

Thanks for your help

Regards

seem to be windows specific, no issues on linux, but I can replicate on windows

In f2d585a

a section was added

                # Skip '*-elf-g++' (crosstool-NG)
                if not gpath.stem.endswith('-elf-g++'):
                    gccpath = str(gpath.resolve())
                    break

But the compiler for esp32 is a -elf-g++ eg .platformio/packages/toolchain-xtensa32/bin/xtensa-esp32-elf-g++

So it cannot find the the compiler and default to CC and fails.

@thinkyhead is there a more exact string you can look for to exclude this crosstool-NG

ok this looks like a good work around to me.

change if not gpath.stem.endswith('-elf-g++'):
to if not "xtensa32" not in str(gpath) and gpath.stem.endswith('-elf-g++'):

Made above changes and now get Invalid syntax error. Latest Marlin 2.1.X bug fix, Windows 10, Vs code PIO and MAB all up to date. Compiling for Neptune 2S with MKS Tinybee. Not proficient in Python, searching all morning for fix to no avail.

the code should end up looking like

                # Skip '*-elf-g++' (crosstool-NG)
                if not "xtensa32" not in str(gpath) and gpath.stem.endswith('-elf-g++'):
                    gccpath = str(gpath.resolve())
                    break

I mad a mistake on the additions to the code. This fix DOES work. Thank you so very much for your time and effort

A PR has been created to fix this.