• Registered: 2025-03-31
  • Posts: 2

Topic: Issues with ChaCha20_Poly1305 Header Inclusion

I'm cross-compiling for an arm-none-eabi-gcc environment and keep getting the error "undefined reference to wc_ChaCha20Poly1305_Decrypt". My c file for my project code includes the headers in this order:

#include <wolfssl/options.h>
#include <wolfssl/wolfcrypt/settings.h>
#include <wolfssl/wolfcrypt/chacha20_poly1305.h>

This is what I'm passing to ./configure:

    ./configure --enable-static --disable-shared --enable-psk --disable-crypttests --disable-examples \
    --host=arm-none-eabi \
    CC=arm-none-eabi-gcc LD=arm-none-eabi-ld \
    AR=arm-none-eabi-ar RANLIB=arm-none-eabi-ranlib \
    CFLAGS="-DNO_WOLFSSL_DIR -DWOLFSSL_USER_IO -DNO_WRITEV -mcpu=cortex-m4 -mthumb -Os -specs=rdimon.specs" \
    CPPFLAGS="-I./" \
    C_EXTRA_FLAGS="-DHAVE_CHACHA -DHAVE_POLY1305 -DTIME_T_NOT_64BIT"

In my project's makefile, I'm linking like this:

PROJ_LDFLAGS += -L/usr/local/lib -lwolfssl

Any ideas as to what I'm doing wrong?

Share

  • Registered: 2021-07-06
  • Posts: 168

Re: Issues with ChaCha20_Poly1305 Header Inclusion

Hi bkeller02,

I expect the function wc_ChaCha20Poly1305_Decrypt to be available with the defines HAVE_CHACHA and HAVE_POLY1305, there are no additional requirements for this function as of 5.7.6.  Just to be sure, can you try replacing these flags with --enable-chacha --enable-poly1305 and let me know if it helps?

If not, please confirm what version of wolfSSL you're using.  Please also try running 

nm -g --defined-only

on your wolfSSL library and confirm whether you see wc_ChaCha20Poly1305_Decrypt in the output.

Thanks,
Kareem

Share

  • Registered: 2025-03-31
  • Posts: 2

Re: Issues with ChaCha20_Poly1305 Header Inclusion

Hi Kareem,

Running nm gave this output for the relevant file:

src_libwolfssl_la-chacha20_poly1305.o:
00000001 T wc_ChaCha20Poly1305_CheckTag
00000293 T wc_ChaCha20Poly1305_Decrypt
0000022f T wc_ChaCha20Poly1305_Encrypt
000001c5 T wc_ChaCha20Poly1305_Final
00000035 T wc_ChaCha20Poly1305_Init
000000bb T wc_ChaCha20Poly1305_UpdateAad
00000119 T wc_ChaCha20Poly1305_UpdateData

With both the HAVE_CHACHA and HAVE_POLY1305 flags defined or when replacing them with --enable-chacha and --enable-poly1305.

I think I'm using 5.7.6, but I'm building the library within a docker container like this:

RUN git clone --depth=1 https://github.com/wolfSSL/wolfssl.git /root/wolfssl && \
    cd /root/wolfssl && \
    ./autogen.sh && \
    ./configure --enable-static --disable-shared --enable-psk --disable-crypttests --disable-examples \
    --host=arm-none-eabi \
    CC=arm-none-eabi-gcc LD=arm-none-eabi-ld \
    AR=arm-none-eabi-ar RANLIB=arm-none-eabi-ranlib \
    CFLAGS="-DNO_WOLFSSL_DIR -DWOLFSSL_USER_IO -DNO_WRITEV -mcpu=cortex-m4 -mthumb -Os -specs=rdimon.specs" \
    CPPFLAGS="-I./" \
    C_EXTRA_FLAGS="-DHAVE_CHACHA -DHAVE_POLY1305 -DTIME_T_NOT_64BIT" && \
    make -j$(nproc) && \
    make install

Is there any issue with this method?

Share

  • Registered: 2021-07-06
  • Posts: 168

Re: Issues with ChaCha20_Poly1305 Header Inclusion

Hi bkeller02,

Thanks for the followup.  Please try running nm on the output library, for example /usr/local/lib/libwolfssl.a.

If you still see wc_ChaCha20Poly1305_Decrypt in the output, try running "ldd" on your application and confirm that it is pointing to the correct wolfSSL library.  If you have a system wolfSSL package installed, try uninstalling it.

Thanks,
Kareem

Share