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

undefined symbol: aes_hw_encrypt #461

Closed
kharalanov opened this issue Mar 16, 2023 · 2 comments
Closed

undefined symbol: aes_hw_encrypt #461

kharalanov opened this issue Mar 16, 2023 · 2 comments

Comments

@kharalanov
Copy link

Hi - I'm compiling and installing awsiotsdk on Intel Arria10 SoC (ARM Cortex-A9).
I'm using buildroot 2023.02. The Linux kernel is v4.14.
I've tried both Python 3.10 and 3.11 as well as GCC 8.5.0 and GCC 10.3.1.
In both cases the compile and installation works fine with single warning about the GCC not supported due to a memcmp related bug reported although it looks like this bug was fixed in those particular versions of the compilers.

Here is the full error:

Python 3.11.2 (main, Mar 15 2023, 13:25:30) [GCC 10.3.1 20210621] on linux
Type "help", "copyright", "credits" or "license" for more information.

import awsiot
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3.11/site-packages/awsiot/init.py", line 14, in
File "/usr/lib/python3.11/site-packages/awscrt/mqtt.py", line 9, in
ImportError: /usr/lib/python3.11/site-packages/_awscrt.cpython-311-arm-linux-gnueabihf.so: undefined symbol: aes_hw_encrypt

Attached is the full build log.
Thanks
awscrt_build_log.txt

@graebm
Copy link
Contributor

graebm commented Mar 16, 2023

This seems similar to #444
Cross-compiling with buildroot isn't something we know how to do yet

@kharalanov
Copy link
Author

Hi @graebm - Thanks for the link to #444. This actually helped. Looks like buildroot or some other config script is not setting correctly the processor type to arm. The only change I made was to add this to crt/CMakeList.txt:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR arm)
I don't get the error anymore and and I can publish to and receive from the AWS IOT Core. I think we can close this issue.

@graebm graebm closed this as completed Mar 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants