Linker issue on esp32s3_devkitc, SDK 1.0.1

[KimBP]

Describe the bug

I'm trying to update a project to Zephyr version 4.4.1 but experience a problem on one of two PCs (both Ubuntu)
The only difference I've found is cmake version being 3.28.3 on the 'working PC' while the failing uses version 4.1.0

If I try to build e.g. hello_word for esp32s3_devkitc,, the failing PC returns errors saying
ld.bfd: cannot find :>: No such file or directory
and
ld.bfd: cannot find :-Os>: No such file or directory

If I change optimization level to e.g DEBUG, the latter becomes :-O2>:

I've located it to CMakeLists.txt. If I comment out the line toolchain_linker_add_compiler_options(${simple_options})
it links.

While printing out ${simple_options} I clearly see the 'bad' arguments with colon.

Can it be related to commit 82990ec which do change compiler_simple_options?

Regression

• This is a regression.

Steps to reproduce

Described above

Relevant log output

Start of linker command:

....zephyr-sdk-1.0.1/gnu/xtensa-espressif_esp32s3_zephyr-elf/bin/xtensa-espressif_esp32s3_zephyr-elf-gcc  -gdwarf-4 ":>" ":-Os>" zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr/zephyr_pre0.elf ....

Bad arguments following gdwarf-4

Impact

Showstopper – Prevents release or major functionality; system unusable.

Environment

Ubuntu

Additional Context

No response

[tejlmand]

this looks like a known CMake defect in CMake v4.1 https://gitlab.kitware.com/cmake/cmake/-/work_items/27133

which CMake version are you using ?

The CMake bug is fix in CMake >=v4.1.1.

[KimBP]

Sounds plausible. Like I write, the P with the problem is running cmake 4.1.0

Due to vacation I won't have access to this particular PC the coming weeks, but I guess we can close the issue for now