Re: 3.0.0 compile failure when SASL is enabled but not TLS (proposed patch)

2015-02-13 Thread Viktor Dukhovni
On Sat, Feb 14, 2015 at 06:17:28AM +, Viktor Dukhovni wrote: > Proposed (fix some date typos in the HISTORY file first): No problem there. > Then make the reported use of the TLS context depend on #ifdef USE_TLS: Too hasty with the #ifdef bits on this one. Take 2: diff --git a/src/smtpd/s

Re: 3.0.0 compile failure when SASL is enabled but not TLS (proposed patch)

2015-02-13 Thread Viktor Dukhovni
On Sat, Feb 14, 2015 at 03:57:19PM +1100, Joshua Root wrote: > In the 3.0.0 release, line 4028 of src/smtpd/smtpd.c references > state->tls_context, but unlike other such references in this file, it is > not wrapped in an #ifdef USE_TLS. This causes compilation to fail when > building with SASL su

3.0.0 compile failure when SASL is enabled but not TLS

2015-02-13 Thread Joshua Root
In the 3.0.0 release, line 4028 of src/smtpd/smtpd.c references state->tls_context, but unlike other such references in this file, it is not wrapped in an #ifdef USE_TLS. This causes compilation to fail when building with SASL support but without TLS: smtpd.c:4028:13: error: no member named 'tls_c