Mailing List Archive

compiling 4.91 under FreeBSD
Had someone this error? Using port:

cc tls.c
In file included from tls.c:122:
tls-openssl.c: In function `tls_refill':
tls-openssl.c:2499: error: structure has no member named `verify_stack'
tls-openssl.c:2502: error: structure has no member named `verify_stack'
tls-openssl.c: In function `tls_close':
tls-openssl.c:2778: error: structure has no member named `verify_stack'
tls-openssl.c:2779: error: structure has no member named `verify_stack'
*** Error code 1
Stop in /usr/ports/mail/exim/work/exim-4.91/build-FreeBSD-i386.

# /usr/local/bin/openssl version
OpenSSL 1.0.2o 27 Mar 2018


--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
> On Apr 16, 2018, at 1:02 PM, Lena--- via Exim-users <exim-users@exim.org> wrote:
>
> Had someone this error? Using port:
>
> cc tls.c
> In file included from tls.c:122:
> tls-openssl.c: In function `tls_refill':
> tls-openssl.c:2499: error: structure has no member named `verify_stack'
> tls-openssl.c:2502: error: structure has no member named `verify_stack'
> tls-openssl.c: In function `tls_close':
> tls-openssl.c:2778: error: structure has no member named `verify_stack'
> tls-openssl.c:2779: error: structure has no member named `verify_stack'
> *** Error code 1
> Stop in /usr/ports/mail/exim/work/exim-4.91/build-FreeBSD-i386.
>
> # /usr/local/bin/openssl version
> OpenSSL 1.0.2o 27 Mar 2018

The structure in question has that field subject to "#ifndef DISABLE_OCSP":

https://github.com/Exim/exim/blob/6372d4c990f39ba6ad84a91af0a3a61a63bd50a3/src/src/tls-openssl.c#L155

so its use should also be similarly subject to the same constraint.

--
Viktor.


--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
Hi!

> Had someone this error? Using port:

Can you provide a

make showconfig

output ? On what FreeBSD version ? I've testbuilded on current, looks OK.

--
pi@opsec.eu +49 171 3101372 2 years to go !

--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
http://home.lerctr.org:8888/data/live-host-ports/2018-04-16_11h54m01s/logs/errors/exim-4.91.log

similar.

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: ler@lerctr.org
US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

?On 4/16/18, 12:09 PM, "Exim-users on behalf of Lena--- via Exim-users" <exim-users-bounces+ler=lerctr.org@exim.org on behalf of exim-users@exim.org> wrote:

Had someone this error? Using port:

cc tls.c
In file included from tls.c:122:
tls-openssl.c: In function `tls_refill':
tls-openssl.c:2499: error: structure has no member named `verify_stack'
tls-openssl.c:2502: error: structure has no member named `verify_stack'
tls-openssl.c: In function `tls_close':
tls-openssl.c:2778: error: structure has no member named `verify_stack'
tls-openssl.c:2779: error: structure has no member named `verify_stack'
*** Error code 1
Stop in /usr/ports/mail/exim/work/exim-4.91/build-FreeBSD-i386.

# /usr/local/bin/openssl version
OpenSSL 1.0.2o 27 Mar 2018


--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/




--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
On 16/04/18 18:12, Viktor Dukhovni via Exim-users wrote:
>> tls-openssl.c: In function `tls_refill':
>> tls-openssl.c:2499: error: structure has no member named `verify_stack'
>> tls-openssl.c:2502: error: structure has no member named `verify_stack'
>> tls-openssl.c: In function `tls_close':
>> tls-openssl.c:2778: error: structure has no member named `verify_stack'
>> tls-openssl.c:2779: error: structure has no member named `verify_stack'
>> *** Error code 1
>> Stop in /usr/ports/mail/exim/work/exim-4.91/build-FreeBSD-i386.
>>
>> # /usr/local/bin/openssl version
>> OpenSSL 1.0.2o 27 Mar 2018
>
> The structure in question has that field subject to "#ifndef DISABLE_OCSP":
>
> https://github.com/Exim/exim/blob/6372d4c990f39ba6ad84a91af0a3a61a63bd50a3/src/src/tls-openssl.c#L155
>
> so its use should also be similarly subject to the same constraint.

Indeed; that's a bug.

Apologies, Lena - you'll need to either add #ifndef guards for those
lines, or build with OCSP support.
--
Cheers,
Jeremy


--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
I had this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227560

Lena--- via Exim-users ????? 2018-04-16 19:02:
> Had someone this error? Using port:
>
> cc tls.c
> In file included from tls.c:122:
> tls-openssl.c: In function `tls_refill':
> tls-openssl.c:2499: error: structure has no member named `verify_stack'
> tls-openssl.c:2502: error: structure has no member named `verify_stack'
> tls-openssl.c: In function `tls_close':
> tls-openssl.c:2778: error: structure has no member named `verify_stack'
> tls-openssl.c:2779: error: structure has no member named `verify_stack'
> *** Error code 1
> Stop in /usr/ports/mail/exim/work/exim-4.91/build-FreeBSD-i386.
>
> # /usr/local/bin/openssl version
> OpenSSL 1.0.2o 27 Mar 2018

--
With best regards,
Max Kostikov

T: +7(952)7927000 | W: https://kostikov.co | BBM: 24CA5DF8
Re: compiling 4.91 under FreeBSD [ In reply to ]
On 2018-04-16 at 20:21 +0200, Max Kostikov via Exim-users wrote:
> I had this
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227560

The experimental DMARC support hard-requires SPF support.

NewStuff:

4. SPF support is promoted from Experimental to mainline status. The template
src/EDITME makefile does not enable its inclusion.

In Local/Makefile, replace EXPERIMENTAL_SPF=yes with SUPPORT_SPF=yes

Looks like the FreeBSD Ports tree has now adapted:

https://github.com/freebsd/freebsd-ports/commit/5c374cf90a31c879d053db12db0c08d830c8f31f

-Phil

--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
On 2018-04-16 at 12:14 -0500, Larry Rosenman via Exim-users wrote:
> http://home.lerctr.org:8888/data/live-host-ports/2018-04-16_11h54m01s/logs/errors/exim-4.91.log

Enable OCSP support. It's on by default in Exim and our test suite
isn't good at ensuring we still compile when various things are
disabled. Instead, we rely upon people testing Release Candidates.

Jeremy has fixed this for the next release, but 4.91 hard-requires
either OCSP or a patch.

(Patches to update the test-suite to handle this cleanly would be
gratefully received, and considered.)

-Phil

--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
Re: compiling 4.91 under FreeBSD [ In reply to ]
On 16.04.2018 21:00, Phil Pennock wrote:
> On 2018-04-16 at 12:14 -0500, Larry Rosenman via Exim-users wrote:
>> http://home.lerctr.org:8888/data/live-host-ports/2018-04-16_11h54m01s/logs/errors/exim-4.91.log
>
> Enable OCSP support. It's on by default in Exim and our test suite
> isn't good at ensuring we still compile when various things are
> disabled. Instead, we rely upon people testing Release Candidates.
>
> Jeremy has fixed this for the next release, but 4.91 hard-requires
> either OCSP or a patch.
>
> (Patches to update the test-suite to handle this cleanly would be
> gratefully received, and considered.)
>
> -Phil
>

I have imported the patch from the upstream that should hopefully fix
the issue in 4.91_2. Thanks for a quick response!