Skip to content

How to build libs2n.so properly? #343

Closed
@zhaokai3000

Description

@zhaokai3000

Confirm by changing [ ] to [x] below:

Known Issue

  • I'm using ATS data type endpoint: the endpoint should look like <prefix>-ats.iot.<region>.amazonaws.com

Platform/OS/Device
What are you running the sdk on?
aarch64 GNU/linux development board.

Describe the question
I have a arm64 linux development board which I wan't to port aws iot sdk to it.
The whole build system use buildroot to build all packages.
There is a libopenssl package (openssl1.1.1) originally. By building this package, it would generate /usr/lib/libcrypto.so.1.1 and /usr/lib/libssl.so.1.1 into target directory and create symlink /usr/lib/libcrypto.so and /usr/lib/libssl.so which points to them. There're some other packages which depends on these two libraries to build.

If I build the aws iot device sdk after building the libopenssl package,it will generate new libcrypto.so and libssl.so and install to /usr/lib directory, which would cause build failure for other packages which depends on the original so files.

If I remove the new libcrypto.so created by aws iot device sdk build process, the application using libs2n.so will encounter build failure for missing some apis which the original libcrypto.so doesn't have.

So it seems that libs2n.so needs some api from aws iot libcrypto.so which the orignal libcrypto.so.1.1 doesn't have, and other packages needs some api from the orignal libcrypto.so.1.1 which the aws iot libcrypto.so doesn't have..

What's the proper way to deal with this?

I wonder if I could configure the aws iot sdk to build libcrypto and libssl statically and build the other libraries shared?

Metadata

Metadata

Assignees

Labels

guidanceQuestion that needs advice or information.response-requestedWaiting on additional info and feedback. Will move to "closing-soon" in 2 days.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions