[openssl-users] Compiling openssl 1.0.2q for OS390-Unix
thiagu.m at gmail.com
Wed Jan 23 15:38:12 UTC 2019
---------- Forwarded message ---------
From: Thiagu Mohan <thiagu.m at gmail.com>
Date: Wed, Jan 23, 2019 at 4:39 PM
Subject: Re: [openssl-users] Compiling openssl 1.0.2q for OS390-Unix
To: Michael Wojcik <Michael.Wojcik at microfocus.com>
Yes I am using the option for Configure as OS390-Unix only and using
c89.sh from tools directory in the openssl tar file.
On Wed, Jan 23, 2019 at 2:50 AM Michael Wojcik <
Michael.Wojcik at microfocus.com> wrote:
> > From: Thiagu Mohan [mailto:thiagu.m at gmail.com]
> > Sent: Tuesday, January 22, 2019 13:02
> > To: Michael Wojcik
> Please reply to the mailing list, and not to me directly.
> > PKCS12_AUTHSAFES_it these symbols must be typedefs.
> I don't know how you came to that conclusion, but it's wrong. A bit of
> digging shows the *_it symbols are used to provide access to global
> variables on platforms which do not automatically resolve non-function
> symbols in shared libraries/objects.
> > On Tue, Jan 22, 2019 at 11:24 PM Thiagu Mohan <thiagu.m at gmail.com>
> > I checked the source of 1.0.2n and 1.0.2q. these symbols are found in
> > in both the sources and not in any other source code.
> Though the util/*.num files are included in the source tarballs, they're
> not really source code. They're created by mkdef.pl. Unfortunately
> mkdef.pl achieves a level of unreadableness that is impressive even by
> Perl standards, so that's not much help.
> I'll be frank: This isn't a problem I've run into before, and I don't have
> time at the moment to try to figure out what's causing it. Maybe someone
> who has more experience in this particular area will chime in.
> You did run Configure for the OS390-Unix target, right? And it's using the
> c89.sh wrapper from the tools directory?
> Michael Wojcik
> Distinguished Engineer, Micro Focus
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the openssl-users