Hi,
Apologies for the delayed response.
Thank you for the suggestions. I will look into both options and follow up with
a patch once I have a solution prepared.
Regards
Sachin
On 20/06/25, 9:31 PM, "Werner Koch" wrote:
On Fri, 20 Jun 2025 10:44, Sachin T said:
> zoslib consists of two static
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 somethi
Hi,
Thanks regarding the EXTRA_LIBS_FOR_BUILD suggestion, I had a follow-up
question.
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 explic
On Tue, 17 Jun 2025 16:34, Sachin T said:
> Hi Gpg team,
>
> Please review patch required for libgpg-error on IBM z/OS platform.
Pretty small now. Cool. I have an improvement:
--8<---cut here---start->8---
Set build specific variable for zOS
* co
Hi Gpg team,
Please review patch required for libgpg-error on IBM z/OS platform.
Patch details
1. mkheader target depends on “zoslib”(specific to z/OS platform) which is
passed via LIBS
2. Renamed structure field ‘environ’ to avoid conflict with environ defined
in z/OS stdlib header.
Re
