Re: Monolith compile verify.c

2020-06-25 Thread Michael Mueller
Thank you so much for the replies. I appreciate the effort, time, and detail. Turns out the warning is created by: -Wextra Only occurs in the older compiler (which we are required to use). Removing the compiler flag worked. Thanks again, Mike On Thu, Jun 25, 2020, 9:42 AM Michael Wojcik

RE: Monolith compile verify.c

2020-06-25 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of > Matt Caswell > Sent: Thursday, June 25, 2020 04:51 > > On 24/06/2020 20:20, Michael Mueller wrote: > > > > Questions > > > > 1. Is the fix valid? > > Seems ok, but it looks like the compiler warning is a bit over

Re: Monolith compile verify.c

2020-06-25 Thread Matt Caswell
On 24/06/2020 20:20, Michael Mueller wrote: > > Questions > > 1. Is the fix valid? Seems ok, but it looks like the compiler warning is a bit over zealous. We have the same pattern in many parts of the code I think without problems. > > 2.  If fix is valid, what are the chances of getting

Re: Monolith compile verify.c

2020-06-24 Thread Salz, Rich via openssl-users
C mandates that any “missing” initializers are as if 0/null were present. {NULL, -1, 'Q', "unused end of list"} this is the change I’d like to offer Turn off the warning.

Monolith compile verify.c

2020-06-24 Thread Michael Mueller
I'm compiling verify.c as a monolith from 1.1.1g. Using gcc 4.8.5 I have no problems. Using gcc 4.3.4 I get a warning which we treat as an error: gcc -c -Wall -Werror -Wextra -idirafter ../../inc -idirafter ../../../../OPENSSL/include/SUSE-Linux -DMONOLITH -DNO_ASN1_OLD -DLINUX -o