On May 11, 2014, at 6:34 PM, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote:
> On Sun, May 11, 2014 at 06:00:38PM -0500, Larry Stone wrote: > >> On the test system, trying to force the new version of OpenSSL (1.0.1g), I >> used: >> make -f Makefile.init makefiles \ >> CCARGS='-DUSE_TLS /usr/local/ssl/include/openssl \ >> -DUSE_SASL_AUTH \ >> -DDEF_COMMAND_DIR=\"/usr/local/sbin\" \ >> -DDEF_CONFIG_DIR=\"/usr/local/etc/postfix\" \ >> -DDEF_DAEMON_DIR=\"/usr/local/libexec/postfix\" \ >> -DHAS_PCRE -I/usr/local/include' \ >> AUXLIBS='L/usr/local/ssl/lib ?lssl ?lcrypto \ >> -L/usr/local/lib -lpcre -L/usr/lib -lresolv? > > The above syntax is incorrect. Try > > ... CCARGS=' > -DUSE_TLS -I/usr/local/ssl/include > -DUSE_SASL_AUTH > -DDEF_COMMAND_DIR=\"/usr/local/sbin\" > -DDEF_CONFIG_DIR=\"/usr/local/etc/postfix\" > -DDEF_DAEMON_DIR=\"/usr/local/libexec/postfix\" > -DHAS_PCRE -I/usr/local/include > ' \ > AUXLIBS=' > -L /usr/local/ssl/lib -lssl -lcrypto > -L/usr/local/lib -lpcre > ' That worked. Thanks. But I don’t understand why. I’m assuming the key difference was on the -DUSE_TLS directive. With the new OpenSSL version, /usr/local/ssl/include contains only the openssl directory which in turn contains all the openssl header files. So how does the path specified behind -DUSE_TLS work? -- Larry Stone lston...@stonejongleux.com http://www.stonejongleux.com/
smime.p7s
Description: S/MIME cryptographic signature
