Hi,
I am routinely building in CI the STM32H563 port using the default configuration provided in its README. Since July 28 I am getting a linker error on the same configuration:
arm-none-eabi-gcc -mcpu=cortex-m33 -mthumb -Os -ffreestanding -fdata-sections -ffunction-sections -g -ggdb -Wall -Wextra -Werror -I. -I../../.. -I../../../src -I../../../src/port -I../../../src/port/stm32 -DSTM32H5 -DTZEN_ENABLED=0 -DENABLE_TLS -DWOLFSSL_USER_SETTINGS -DWOLFSSL_WOLFIP -I../../../../wolfssl -DENABLE_HTTPS -DWOLFIP_ENABLE_HTTP -DENABLE_SSH -DWOLFSSH_USER_SETTINGS -I../../../../wolfssh -DENABLE_MQTT_BROKER -DWOLFMQTT_USER_SETTINGS -I../../../../wolfmqtt startup.o ivt.o syscalls.o main.o ../../../src/port/stm32/stm32_eth.o ../../../src/wolfip.o tls_server.o ../../../src/port/wolfssl_io.o ../../../src/http/httpd.o ../../../../wolfssl/wolfcrypt/src/aes.o ../../../../wolfssl/wolfcrypt/src/sha.o ../../../../wolfssl/wolfcrypt/src/sha256.o ../../../../wolfssl/wolfcrypt/src/sha512.o ../../../../wolfssl/wolfcrypt/src/hmac.o ../../../../wolfssl/wolfcrypt/src/hash.o ../../../../wolfssl/wolfcrypt/src/kdf.o ../../../../wolfssl/wolfcrypt/src/random.o ../../../../wolfssl/wolfcrypt/src/ecc.o ../../../../wolfssl/wolfcrypt/src/asn.o ../../../../wolfssl/wolfcrypt/src/coding.o ../../../../wolfssl/wolfcrypt/src/wc_port.o ../../../../wolfssl/wolfcrypt/src/memory.o ../../../../wolfssl/wolfcrypt/src/wolfmath.o ../../../../wolfssl/wolfcrypt/src/sp_int.o ../../../../wolfssl/wolfcrypt/src/sp_c32.o ../../../../wolfssl/wolfcrypt/src/sp_cortexm.o ../../../../wolfssl/src/ssl.o ../../../../wolfssl/src/tls.o ../../../../wolfssl/src/tls13.o ../../../../wolfssl/src/internal.o ../../../../wolfssl/src/keys.o ../../../../wolfssl/src/wolfio.o ../../../../wolfssl/wolfcrypt/src/chacha.o ../../../../wolfssl/wolfcrypt/src/chacha20_poly1305.o ../../../../wolfssl/wolfcrypt/src/poly1305.o ../../../../wolfssl/wolfcrypt/src/rsa.o ../../../../wolfssl/wolfcrypt/src/signature.o ssh_server.o ../../../src/port/wolfssh_io.o ../../../../wolfssh/src/ssh.o ../../../../wolfssh/src/internal.o ../../../../wolfssh/src/io.o ../../../../wolfssh/src/keygen.o ../../../../wolfssh/src/log.o ../../../../wolfssh/src/port.o mqtt_broker.o ../../../../wolfmqtt/src/mqtt_broker.o ../../../../wolfmqtt/src/mqtt_client.o ../../../../wolfmqtt/src/mqtt_packet.o ../../../../wolfmqtt/src/mqtt_socket.o -nostdlib -T target.ld -Wl,-gc-sections -Wl,--start-group -lc -lm -lgcc -lnosys -Wl,--end-group -o app.elf
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: ../../../../wolfssh/src/internal.o: in function `PrepareUserAuthRequestEcc':
/home/devel/wolf/wolfip/src/port/stm32h563/../../../../wolfssh/src/internal.c:16945:(.text.SendUserAuthRequest+0x2dc): undefined reference to `GetOpenSshKey'
/usr/lib/gcc/arm-none-eabi/13.2.1/../../../arm-none-eabi/bin/ld: ../../../../wolfssh/src/internal.o: in function `PrepareUserAuthRequestRsa':
/home/devel/wolf/wolfip/src/port/stm32h563/../../../../wolfssh/src/internal.c:16485:(.text.SendUserAuthRequest+0x342): undefined reference to `GetOpenSshKey'
collect2: error: ld returned 1 exit status
make: *** [Makefile:501: app.elf] Error 1
from a clean build directory. I think the most probable cause is commit https://github.com/wolfSSL/wolfssh/tree/029d412e1f5136169de330e46f529ef7116e92af on wolfSSL, because the timeline does fit into the sudden appearance of the failure, but I am not certain that this is the only cause. It is likely that some default configuration changed in one of the sibling repositories, and something needs to be changed (e.g. in user_settings.h of the port), but I'm not sure where I should modify it.
Hi,
I am routinely building in CI the STM32H563 port using the default configuration provided in its README. Since July 28 I am getting a linker error on the same configuration:
from a clean build directory. I think the most probable cause is commit https://github.com/wolfSSL/wolfssh/tree/029d412e1f5136169de330e46f529ef7116e92af on wolfSSL, because the timeline does fit into the sudden appearance of the failure, but I am not certain that this is the only cause. It is likely that some default configuration changed in one of the sibling repositories, and something needs to be changed (e.g. in user_settings.h of the port), but I'm not sure where I should modify it.