From sachin.t at ibm.com Mon Dec 1 06:05:10 2025 From: sachin.t at ibm.com (Sachin T) Date: Mon, 1 Dec 2025 05:05:10 +0000 Subject: [PATCH libgcrypt] Add support for IBM z/OS In-Reply-To: <87y0nr7xzt.fsf@haruna.fsij.org> References: <87y0nr7xzt.fsf@haruna.fsij.org> Message-ID: 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 Date: Friday, 28 November 2025 at 6:51?AM To: Sachin T Cc: GNU Libgcrypt Development 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= 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? -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From gniibe at fsij.org Tue Dec 2 07:51:45 2025 From: gniibe at fsij.org (NIIBE Yutaka) Date: Tue, 02 Dec 2025 15:51:45 +0900 Subject: [PATCH libgcrypt] Add support for IBM z/OS In-Reply-To: References: <87y0nr7xzt.fsf@haruna.fsij.org> Message-ID: <87pl8xs7em.fsf@haruna.fsij.org> Hello, again, Sachin T wrote: > Thanks for reviewing the changes. I pushed other changes (libtool macro, longlong.h and secmem.c). Let me have some time for configure.ac. > The wrapper approach worked for me. Good. Please go ahead with the wrapper approach. If the EXTRA_LIBS_FOR_BUILD is only for GnuPG, it would be acceptable. My concern is that it will be for (almost) all packages you build. > 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 see. If the wrapper approach will be found good, we can consider about reverting the part of libgpg-error change. --