Hello, Thanks for reviewing the changes.
The wrapper approach worked for me. I also wanted to mention that libgpg-error already uses EXTRA_LIBS_FOR_BUILD in its configure.ac for z/OS, so using the same method in libgcrypt would keep things consistent across both projects. I can go with the approach you recommend. Regards, Sachin From: NIIBE Yutaka <[email protected]> Date: Friday, 28 November 2025 at 6:51 AM To: Sachin T <[email protected]> Cc: GNU Libgcrypt Development <[email protected]> Subject: [EXTERNAL] Re: [PATCH libgcrypt] Add support for IBM z/OS Hello, I have a comment about EXTRA_LIBS_FOR_BUILD. Sachin T wrote: > 1. [...] > EXTRA_LIBS_FOR_BUILD via pkg-config/zoslib for external library linking > 2. [...] > cipher/Makefile.am, doc/Makefile.am: Append $(EXTRA_LIBS_FOR_BUILD) to > gost-s-box and yat2m link lines so build-host helper programs link > correctly with z/OS-specific libraries during the build. If I were developing/maintaining those packages for a POSIX-like Operating System which needs to care about specific libraries and/or headers, I'd consider about a compiler script to use as CC (and put linking procedure with specific libraries into that script). Then, I'd specify CC=<THE_PATH_TO_THE_SCRIPT> for configure (or CC_FOR_BUILD). Or else, it would end up to ask all software to put similar patches. Could you please consider this approach? --
_______________________________________________ Gnupg-devel mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-devel
