Hi Patrice,

Thank you for email! I am the current maintainer of GNU Libtool.

I have a few suggestions, but I do not have a solution for you. For
easier debugging, I suggest tarring the build directory entirely and
saving that after each CI run rather than individual files. It will
help verify what is being generated and where.

For each of the OSes that you have issues with, here are my thoughts:
- MacOS, I expect another flag, like -L, needs to be set to locate it.
- OpenBSD likely needs to utilize the commands [1] that you found. Here
is a test case in libtool that utilizes it [2], which was developed for
testing local programs and libraries.
- Windows may need an additional option in LT_INIT for dlopening,
win32-dll [3][4].

Here is some more documentation [5] for dlopening with libtool that I
expect you have already read, but it may help others.

[1] https://www.gnu.org/software/libtool/manual/libtool.html#Invoking-libtool [2] https://cgit.git.savannah.gnu.org/cgit/libtool.git/tree/tests/bug_71489.at [3] https://www.gnu.org/software/libtool/manual/libtool.html#index-LT_005fINIT
[4] https://cgit.git.savannah.gnu.org/cgit/libtool.git/tree/tests/demo.at
[5] https://www.gnu.org/software/libtool/manual/libtool.html#Dlopened-modules-1

--
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

Attachment: OpenPGP_0x6570EA01146F7354.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to