Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ESP32: Multiple Symbol definition with CONFIG_ESP32_WIFI_MBEDTLS_CRYPTO enabled #86447

Open
phb98 opened this issue Feb 28, 2025 · 0 comments
Open
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug platform: ESP32 Espressif ESP32

Comments

@phb98
Copy link

phb98 commented Feb 28, 2025

Describe the bug
Build fails with multiple symbol definitions when CONFIG_ESP32_WIFI_MBEDTLS_CRYPTO is enabled. Specifically, there are conflicts between functions defined in both aes-omac1.c and crypto_mbedtls.c:
omac1_aes_vector
omac1_aes_128_vector
omac1_aes_128

The source files list is in hal/espressif/zephyr/esp32s3/CMakeLists.txt where CONFIG_MBEDTLS_MAC_CMAC_ENABLED is referenced but doesn't exist in any Kconfig I have searched.

Workaround
Commenting out this line makes it compile successfully:

if(NOT CONFIG_MBEDTLS_MAC_CMAC_ENABLED)
    set(CRYPTO_SRCS ${CRYPTO_SRCS} "${WPA_SUPPLICANT_COMPONENT_DIR}/src/crypto/aes-omac1.c")
endif()

To Reproduce
Build for ESP32S3 with CONFIG_ESP32_WIFI_MBEDTLS_CRYPTO enabled

Environment:

  • HAL Espressif commit id: 202c59552dc98e5cd02386313e1977ecb17a131f

Addition Context

  • I'm not quite familar with mbedtls source files, so please correct me if my assumption was incorrect.
@phb98 phb98 added the bug The issue is a bug, or the PR is fixing a bug label Feb 28, 2025
@henrikbrixandersen henrikbrixandersen added the platform: ESP32 Espressif ESP32 label Mar 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug platform: ESP32 Espressif ESP32
Projects
None yet
Development

No branches or pull requests

3 participants