On Fri, 20 Jun 2025 10:44, Sachin T said: > zoslib consists of two static libraries and one separate object > file. Due to a z/OS linker limitation, the .o file can’t be included > inside an archive , it may get ignored unless one of its symbols is > explicitly referenced.
I think we have something like this also for an older SunOS or so. The solution was to explictly reference the symbol for the main code. I think this was/is in Libgcrypt but I can't remember. But no problem if you already have a solution. > Or would you prefer this logic be handled entirely within configure.ac? I think it better to put this into configure.ac - this also documents the need for them. +case "$build_os" in + *zOS*) + EXTRA_LIBS_FOR_BUILD=-lzoslib -lzoslib-supp <lib_path>/celquopt.s.o + ;; Is there any standard <lib_path> or can this be figured out at configure run time? Another option would be to add it to autogen.rc and extend autogen.sh with a --build-zos option like we did for Windows. Shalom-Salam, Werner -- The pioneers of a warless world are the youth that refuse military service. - A. Einstein
openpgp-digital-signature.asc
Description: PGP signature
_______________________________________________ Gnupg-devel mailing list Gnupg-devel@gnupg.org https://lists.gnupg.org/mailman/listinfo/gnupg-devel
