Portability issues #7

Closed
opened 2024-08-31 21:35:13 +02:00 by 7882249 · 1 comment

I tried using the pre-compiled binaries from https://forge.soutade.fr/soutade/-/packages/generic/libgourou/0.8.6/files/10, but I ran into the issue of not having OpenSSL v3 installed:

$ ./libgourou_utils_0.8.6/adept_activate
./libgourou_utils_0.8.6/adept_activate: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory

I do have OpenSSL installed, but it’s from an older release:

$ openssl version
OpenSSL 1.0.2k-fips 26 Jan 2017

Could you please include pre-compiled binaries of OpenSSL as either a static or shared library in the release tarball as well?

Additionally, based on the README, it looks like I need to manually set up the LD_LIBRARY_PATH for the CLI tools to correctly load the libgourou library. Is there a specific reason for relying on this behavior instead of hard-coding the library search path using something like -Wl,-rpath,$ORIGIN during compilation? If that’s not the case, it could improve portability.

Since I was unable to use the pre-compiled binaries, I attempted to compile it myself:

$ git clone https://forge.soutade.fr/soutade/libgourou
$ cd libgourou
$ make update_lib
./scripts/update_lib.sh
Some libraries are missing. You must run this script at the top of the libgourou working directory.
./lib/setup.sh must be called first (make all)
make: *** [Makefile:66: update_lib] Error 1

It states that I should run ./lib/setup.sh first, but this script doesn’t seem to exist:

$ ./lib/setup.sh
bash: ./lib/setup.sh: No such file or directory

Looks like I can't compile the library either.

I tried using the pre-compiled binaries from https://forge.soutade.fr/soutade/-/packages/generic/libgourou/0.8.6/files/10, but I ran into the issue of not having OpenSSL v3 installed: ``` $ ./libgourou_utils_0.8.6/adept_activate ./libgourou_utils_0.8.6/adept_activate: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory ``` I do have OpenSSL installed, but it’s from an older release: ``` $ openssl version OpenSSL 1.0.2k-fips 26 Jan 2017 ``` Could you please include pre-compiled binaries of OpenSSL as either a static or shared library in the release tarball as well? Additionally, based on the README, it looks like I need to manually set up the `LD_LIBRARY_PATH` for the CLI tools to correctly load the `libgourou` library. Is there a specific reason for relying on this behavior instead of hard-coding the library search path using something like `-Wl,-rpath,$ORIGIN` during compilation? If that’s not the case, it could improve portability. Since I was unable to use the pre-compiled binaries, I attempted to compile it myself: ``` $ git clone https://forge.soutade.fr/soutade/libgourou $ cd libgourou $ make update_lib ./scripts/update_lib.sh Some libraries are missing. You must run this script at the top of the libgourou working directory. ./lib/setup.sh must be called first (make all) make: *** [Makefile:66: update_lib] Error 1 ``` It states that I should run `./lib/setup.sh` first, but this script doesn’t seem to exist: ``` $ ./lib/setup.sh bash: ./lib/setup.sh: No such file or directory ``` Looks like I can't compile the library either.
Owner

Hi,

Sorry for the delay.

Precompiled binaries including OpenSSL3 are available using AppImage.

LD_LIBRARY_PATH is not necessary if you install libgourou (make install). I'll not hardcode it in Makefile.

Sorry, It's not ./lib/setup.sh, but ./scripts/setup.sh, I just fixed this typo error.

For your usecase, I created a branch openssl3 that download and statically link OpenSSL3 to libgourou.

Best regards

Hi, Sorry for the delay. Precompiled binaries including OpenSSL3 are available using AppImage. LD_LIBRARY_PATH is not necessary if you install libgourou (make install). I'll not hardcode it in Makefile. Sorry, It's not `./lib/setup.sh`, but `./scripts/setup.sh`, I just fixed this typo error. For your usecase, I created a branch `openssl3` that download and statically link OpenSSL3 to libgourou. Best regards
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: soutade/libgourou#7
No description provided.