v2.3.3 rc1 - Error: sieve: !!BUG!!: Binary compiled from dovecot.sieve is still corrupt

[James]

On 28/09/2018 12:38, Aki Tuomi wrote:

>>>>> It was studio cc.  gcc doesn't make it through configure and I
>>>>> didn't ask why.
>>>> Can you share a little bit more info on how did the compile (or
>>>> configure even) fail with gcc on Solaris 11?
>>>
>>> $ ./configure $ARGS
>>> ...
>>> checking Linux compatible mremap()... no
>>> checking whether shared mmaps get updated by write()s... no
>>> checking whether fd passing works... no
>>> configure: error: fd passing is required for Dovecot to work
>>>
>>> Which in the log corresponds to:
>>>
>>> configure:22685: ./conftest
>>> ./configure[2026]: eval: line 1: 22335: Memory fault(coredump)
>>>
>>>
>>> Appears to the option "-mfunction-return=thunk" that cause the
>>> problem, remove and no core dump.

If you thunk that was all think again.  My gcc builds fail to link 
ending with lots of undefined symbols.  It is probably libtool 
obstructing portability but I have an easy solution of using another 
compiler and ignoring libtool.



> You can use --disable-harderning to disable these things.

--disable-hardening