similar to: trouble compiling Dovecot 2.2.31 on Solaris 10 SPARC - libssl_iostream_openssl.so is not portable!

attempting to compile dovecot 2.2.31 on Sun/Oracle Solaris 10 SPARC. configure goes fine. First sign of problems during compile is with this warning: ............................................... *** libssl_iostream_openssl.so is not portable! ............................................... actual ERRORS - Soon, compile errors out with undefined symbols. Output at bottom of note.

Jerry Kemp <dovecot at oryx.us> wrote: > same ENV variable setup and configure statement as originally used, but again, :( > ended up failing here: > .......................................................................... > libtool: link: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 >

I'm done. Good to go. Good compile + new binaries all built against the latest OpenSSL libraries. Big thank you to James, Joseph Tam and Aki Tuomi who game me pointers and kept me in the right direction. ........................................................................ These are the settings that made everything work for me. First, needed a current, up-to-date version of OpenSSL

Dear Dovecot developers! This problem already existed some years ago, has been fixed, and now it's there again in Dovecot 2.2.25 (2.2.24 was fine). I'm running CentOS 6 with a custom OpenSSL installation in /usr/local/ssl Therefore, Dovecot is configured like this: env SSL_CFLAGS="-I/usr/local/ssl/include" SSL_LIBS="-L/usr/local/ssl/lib -Wl,-R/usr/local/ssl/lib -lcrypto

On 25/08/2017 04:52, Jerry Kemp wrote: Hello Jerry, > attempting to compile dovecot 2.2.31 on Sun/Oracle Solaris 10 SPARC. It worked for me so you should make it to your goal. > configure goes fine. First sign of problems during compile is with > this warning: > > ............................................... > *** libssl_iostream_openssl.so is not portable! That's

Aki Tuomi <aki.tuomi at dovecot.fi> writes: > &gt; I simulated your compile arguments as best as I could, and compared the libtool > &gt; command in my compile logs with your's. > &gt; > &gt; (mine) > &gt; Mine: -lssl -lcrypto -lrt -lnsl -lsocket -lsendfile > &gt; > &gt; (your's) > &gt; -lcrypto -lrt -lnsl -lsocket

Hello Dovecot users! There seems to be a new dependency in some modules (eg, lib-storage, libdovecot-lda, libdovecot-ssl) on OpenSSL. In Dovecot 2.0, those modules didn't require OpenSSL, but 2.1 does. For the linking process the path to the OpenSSL library isn't specified properly (SSL_LIBS). Dovecot fails to build if OpenSSL is in a non-standard path. (Haven't checked if SSL_CFLAGS

I'm having an issue with Thunderbird (and Opera) and Dovecot SSL on a Solaris 10. My OS is Solaris 10 6/06 x86 (running in 64-bit mode) using ZFS (disk mirror) as the filesystem for my users. Dovecot version is 1.0rc7 (logs below are from 1.0rc6). First the connection asks if the SSL-certificate should be accepted, accepting it seems to work but then nothing happens. Thunderbird is

Am 31.05.2017 um 15:24 schrieb Timo Sirainen: > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.30.1.tar.gz.sig > > Due to some release process changes I didn't notice that one important bugfix wasn't included in the v2.2.30 release branch before I made the release. So fixing it here with v2.2.30.1. Also included another

v2.1's imap/pop3 processes are linked with OpenSSL by default, because of imapc/pop3c storages. I wonder if you notice any actual (system-global) memory usage reduction when compiling without those and you have thousands of imap processes? ./configure --with-storages=mdbox sdbox maildir mbox cydir I guess I could try it myself also but maybe someone else wanting to reduce memory usage is

Am 31.05.2017 um 16:35 schrieb Timo Sirainen: > On 31 May 2017, at 16.53, Reindl Harald <h.reindl at thelounge.net > <mailto:h.reindl at thelounge.net>> wrote: >> >> LTO build is as broken as 2.2.30 >> >> libtool: link: ( cd ".libs" && rm -f "lib10_quota_plugin.la" && ln -s >> "../lib10_quota_plugin.la"

Hello, I am a complete newbie to dovecot, but do have reasonable experience in compiling Unix/Linux software. I am currently trying to do a cross-compile of dovecot-2.29.1 to be used on my home office Thecus NAS (host: Thecus kernel 2.6.33 on 32-bit Intel Atom: "i686-nptl-linux-gnu"; my build machine has Ubuntu 16.04.2 LTS) "from ground up", i.e. I need to build and

Hi, I am running into a interesting issue with Dovecot. I compiled Dovecot 2.0.7 with LD_RUN_PATH set to /xsys/lib and it was able to find and link against the correct OpenSSL libraries (/xsys/lib), the generated Makefile look OK. Here is a snippet of the SSL cflags and libs. SSL_CFLAGS = -I/xsys/include SSL_LIBS = -L/xsys/lib -lssl -lcrypto -ldl After I compil, install and run Dovecot I

Hello, I tried to compile Dovecot 2.2.5 on Debian 6 with an alternate OpenSSL installation located at /usr/local/ssl A compilation with CPPFLAGS="-I/usr/local/ssl/include" \ LDFLAGS="-L/usr/local/ssl/lib -Wl,-rpath=/usr/local/ssl/lib" \ SSL_LIBS="-L/usr/local/ssl/lib -Wl,-rpath=/usr/local/ssl/lib" \ ./configure \ --prefix=/opt/dovecot-2.2.5 \ --enable-asserts \

# doveconf -a # 2.2.13: /etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 6: Unknown setting: ssl doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 35: Invalid size: $default_vsz_limit # grep default_vsz_limit

Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >> ldd /usr/local/Dovecot-2.2.25/lib/dovecot/libssl_iostream_openssl.so >> linux-gate.so.1 => (0x00e8c000) >> libcrypto.so.1.0.0 => not found >> libssl.so.1.0.0 => not found >> librt.so.1 => /lib/librt.so.1 (0x00be4000) >> libc.so.6 => /lib/libc.so.6

Hello! I have a question how about JIT-ed code and the C++ compiler compatibily. My project (www.baadengine.org) will use llvm and we will provide integration of JIT-ed code directly into C++ code. This means that C++ code can call JIT code just like any other code and JIT-ed code can call C++ code. We will compile to your bytecode from our BSF format. The question is if it is possible this

Hi Aki, # dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql -- On June 5, 2017 8:59:08 AM

I have just uploaded a test release of 1.2.3. It includes numerous fixes from the OpenBSD team and should fix the stupid configure bugs of 1.2.2p1. http://violet.ibs.com.au/openssh/files/test/ A detailed ChangeLog is in the directory. Please report successes and failures. Regards, Damien Miller -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller -

Hello I have 2.2.18 built with: ./configure \ --prefix="$prefix" \ --bindir="$prefix/bin" \ --sbindir="$prefix/bin" \ --sysconfdir="/etc" \ --with-storages="maildir,imapc,pop3c" \ --without-vpopmail \ --without-ldap I'm attempting to sync (backup) from another Dovecot server running version 2.0.21: Both servers