[openssl-project] OS/X builds failing

2018-02-09 Thread Matt Caswell
The new travis OS/X builds are failing with this: -MT apps/enc.o -c -o apps/enc.o apps/enc.c apps/enc.c:567:54: error: format specifies type 'uintmax_t' (aka 'unsigned long') but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] BIO_printf(bio_err, "bytes read

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Andy Polyakov
> apps/enc.c:568:54: error: format specifies type 'uintmax_t' (aka > 'unsigned long') but the argument has type 'uint64_t' (aka 'unsigned > long long') [-Werror,-Wformat] > BIO_printf(bio_err, "bytes written: %8ju\n", > BIO_number_written(out)); >

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Viktor Dukhovni
> On Feb 9, 2018, at 5:15 AM, Matt Caswell wrote: > > The new travis OS/X builds are failing with this: > > -MT apps/enc.o -c -o apps/enc.o apps/enc.c > apps/enc.c:567:54: error: format specifies type 'uintmax_t' (aka > 'unsigned long') but the argument has type 'uint64_t'

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Viktor Dukhovni
> On Feb 9, 2018, at 12:39 PM, Kurt Roeckx wrote: > > We document printf to be like the C standard, so it should be > intmax_t, not int64_t, or we need to fix the documentation. I don't think we get to coöpt "j" for another purpose, if we we want a letter format for int64t,

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Viktor Dukhovni
> On Feb 9, 2018, at 11:23 AM, Richard Levitte wrote: > > From those errors, it looks to me like uintmax_t isn't 64-bit on that > Mac OS/X machine, unless 'unsigned long' and 'unsigned long long' are > the same. No, the compiler is not telling you they're not actually the

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Andy Polyakov
>> apps/enc.c:568:54: error: format specifies type 'uintmax_t' (aka >> 'unsigned long') but the argument has type 'uint64_t' (aka 'unsigned >> long long') [-Werror,-Wformat] >> BIO_printf(bio_err, "bytes written: %8ju\n", >> BIO_number_written(out)); >>

Re: [openssl-project] Draft Travel Reimbursement policy

2018-02-09 Thread Salz, Rich
Any commentary on this? Otherwise I’ll do a (two-week) vote next week. From: Rich Salz Reply-To: "openssl-project@openssl.org" Date: Monday, January 29, 2018 at 11:18 AM To: "openssl-project@openssl.org" Subject:

Re: [openssl-project] OS/X builds failing

2018-02-09 Thread Andy Polyakov
For the record. I don't generally appreciate fast commits, but I feel like 100 times stronger when it comes to public headers [naturally in supported or minor release] and I can't qualify 19 minutes turnaround for merge request as appropriate. ___