1 Reply by robertjdac

(3 replies, posted in wolfSSL)

I attached the user_settings.h I used. I have it in the root of my wolfssl folder where I am running all the configure/make commands from (Maybe this is the problem, finding the wrong user_settings.h?)

I am building version 5.8.4.

If I just run ./configure --host=x86_64-lynxos --enable-usersettings, I get errors in wolfcrypt/types.h due to sign/unsigned compare (-Werror=sign-compare) on line 528.

So I ran this:
./configure --host=x86_64-lynxos --enable-usersettings EXTRA_CLAGS="-Wno-error -Wno-error=sign-compare"

That got past that error, but hit another one in wolfcrypt/src/aes.c line 51.. "inlining failed in call to 'always_inline' '_mm_aesimc_si128'.

The only way I can get everything to build properly is this way:

./configure --host=x86_64-lynxos --enable-wolfssh --enable-keygen --enable-intelasm --disable-examples --disable-crypttests --enable-aesni --enable-static EXTRA_CFLAGS="-Wno-error -Wno-error=sign-compare -DSIZEOF_LONG=8"

Then modify options.h to add the WOLFSSL_NO_ATOMIC_H.

I can convert this into a support ticket email in a bit, Thank you.

Go to forum: wolfSSL

2 Topic by robertjdac

(3 replies, posted in wolfSSL)

Hello, I'm configuring wolfssl 5.8.4 with the following command, with the intent to deploy it to an embedded RTOS (LynxOS). I'm doing this on my Linux host, but have sourced the LyxnOS toolchain so that I am using their gcc and toolchain.

./configure --host=x86_64-lynxos --enable-wolfssh --enable-keygen --enable-intelasm --disable-examples --disable-crypttests --enable-aesni --enable-static --enable-usersettings

This passes, but when I call make, I get the following error:
wolfcrypt/src/sm3_asm.S:26:2: error: #error "See https://github.com/wolfSSL/wolfsm for implementation of this file"
   26 | #error "See https://github.com/wolfSSL/wolfsm for implementation of this file"

This error is thrown if WOLFSSL_SM3 is defined. This is strange, since I am not defining it in my user_settings.h nor am I enabling it, and the help page suggests sm3 is disabled by default.

So anyway, I then took out --enable-usersettings and allowed configure to generate the options.h for me. I then ran make and it compiled successfully. So I figured it's something wrong in my user_settings.h

I then copy/pasted all the #defines from the generated options.h to my user_settings.h, and then re-ran configure with --enable-usersettings. I ran make, and same errorsue, even though I am using all the same variables from the generated options.h.

Any ideas why this might be happening? I'm trying to use my own user_settings.h since I need to disable some features for Lynx specifically, eg, Lynx does not have stdatomic.h.

Go to forum: wolfSSL