<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p dir="ltr" style="text-align: left; text-indent: 0px;"><span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Hello,</span></p>
<p style="text-align: left; text-indent: 0px;"><span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Thanks for reviewing the changes.</span></p>
<p style="text-align: left; text-indent: 0px;"><span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">The wrapper approach worked for me.<br>
I also wanted to mention that libgpg-error already uses <code style="font-family: Aptos, Arial, Helvetica, sans-serif;">
EXTRA_LIBS_FOR_BUILD</code> in its <code style="font-family: Aptos, Arial, Helvetica, sans-serif;">
configure.ac</code> for z/OS, so using the same method in libgcrypt would keep things consistent across both projects.</span></p>
<p style="text-align: left; text-indent: 0px;"><span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">I can go with the approach you recommend.</span></p>
<p style="text-align: left; text-indent: 0px;"><span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Regards,<br>
Sachin</span></p>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div dir="ltr" style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="mail-editor-reference-message-container">
<div class="ms-outlook-mobile-reference-message skipProofing">
<meta name="Generator" content="Microsoft Exchange Server">
</div>
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>NIIBE Yutaka <gniibe@fsij.org><br>
<b>Date: </b>Friday, 28 November 2025 at 6:51 AM<br>
<b>To: </b>Sachin T <sachin.t@ibm.com><br>
<b>Cc: </b>GNU Libgcrypt Development <gnupg-devel@gnupg.org><br>
<b>Subject: </b>[EXTERNAL] Re: [PATCH libgcrypt] Add support for IBM z/OS<br>
<br>
</div>
<div class="PlainText" style="font-size: 11pt;">Hello,<br>
<br>
I have a comment about EXTRA_LIBS_FOR_BUILD.<br>
<br>
Sachin T wrote:<br>
> 1.<br>
[...]<br>
> EXTRA_LIBS_FOR_BUILD via pkg-config/zoslib for external library linking<br>
> 2.<br>
[...]<br>
> cipher/Makefile.am, doc/Makefile.am: Append $(EXTRA_LIBS_FOR_BUILD) to<br>
> gost-s-box and yat2m link lines so build-host helper programs link<br>
> correctly with z/OS-specific libraries during the build.<br>
<br>
If I were developing/maintaining those packages for a POSIX-like<br>
Operating System which needs to care about specific libraries and/or<br>
headers, I'd consider about a compiler script to use as CC (and put<br>
linking procedure with specific libraries into that script). Then, I'd<br>
specify CC=<THE_PATH_TO_THE_SCRIPT> for configure (or CC_FOR_BUILD).<br>
<br>
Or else, it would end up to ask all software to put similar patches.<br>
<br>
Could you please consider this approach?<br>
--<br>
</div>
</div>
</body>
</html>