[Bug 281692] devel/xtensa-esp-elf: xtensa-esp32-elf-gcc missing, ESP32 only?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281692

            Bug ID: 281692
           Summary: devel/xtensa-esp-elf: xtensa-esp32-elf-gcc missing,
                    ESP32 only?
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: leres@freebsd.org
          Reporter: ohartmann@walstatt.org
             Flags: maintainer-feedback?(leres@freebsd.org)
          Assignee: leres@freebsd.org

Tried devel/xtensa-esp-elf with recent pulled ESP-IDF release/v5.3.

In most projects, examples and so on, using the ESP-IDF results in pulling in

tools/cmake/toolchain-esp32XX.cmake

depending on the ESP MCU arch choosen, i.e for esp32 it will be

tools/cmake/toolchain-esp32.cmake

or for TYPE=esp32s3

tools/cmake/toolchain-esp32s3.cmake

For ESP32 and tools/cmake/toolchain-esp32.cmake

cmake sets certain variables for the toolchain usage:

[...]
set(CMAKE_C_COMPILER xtensa-esp32-elf-gcc)
set(CMAKE_CXX_COMPILER xtensa-esp32-elf-g++)
set(CMAKE_ASM_COMPILER xtensa-esp32-elf-gcc)
set(_CMAKE_TOOLCHAIN_PREFIX xtensa-esp32-elf-)
...
[...]

The recent incarnation of the port installs, for instance, 

bin/xtensa-esp-elf-gcc,

so the gcc required by the ESP-IDF will be missed without any further action
taken.

I was wondering if this could be fixed by simply symbolic linking the
appropriate binary.

Support for RISC-V 32 is completely missing, isn't it?

-- 
You are receiving this mail because:
You are the assignee for the bug.