Bug 1813 - Cannot compile on Mac OS X with non-default OpenSSL
Summary: Cannot compile on Mac OS X with non-default OpenSSL
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Build system (show other bugs)
Version: 5.6p1
Hardware: All Mac OS X
: P2 minor
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-01 16:52 AEST by Douglas Stebila
Modified: 2016-08-02 10:40 AEST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Stebila 2010-09-01 16:52:58 AEST
I was trying to compile OpenSSH with a different OpenSSL installation.  However, OpenSSH's ./configure command kept failing with the error listed below.  I have included the full sequence of shell commands I used.

$ tar zxf openssl-1.0.0a.tar.gz
$ cd openssl-1.0.0a
$ ./Configure --prefix=/Users/dstebila/Downloads/dev/build darwin64-x86_64-cc
...
$ make
$ make install
$ cd ..
$ tar zxf openssh-SNAP-20100901.tar.gz
$ cd openssh
$ ./configure --prefix=/Users/dstebila/Downloads/dev/build --with-ssl-dir=/Users/dstebila/Downloads/dev/build
...
checking build system type... x86_64-apple-darwin10.4.0
...
checking OpenSSL header version... 1000001f (OpenSSL 1.0.0a 1 Jun 2010)
checking OpenSSL library version... 9080cf (OpenSSL 0.9.8l 5 Nov 2009)
checking whether OpenSSL's headers match the library... no
configure: error: Your OpenSSL headers do not match your
library. Check config.log for details.
...

I also tried adding LDFLAGS and CPPFLAGS to the ./configure command as indicated below, but the same error occurred.

$ ./configure --prefix=/Users/dstebila/Downloads/dev/build --with-ssl-dir=/Users/dstebila/Downloads/dev/build LDFLAGS=-L/Users/dstebila/Downloads/dev/build/lib CPPFLAGS=-I/Users/dstebila/Downloads/dev/build/include
Comment 1 Damien Miller 2011-05-23 12:35:38 AEST
There are probably more details in config.log - could you have a look there to see if there are any more clues to why this went awry?
Comment 2 Damien Miller 2015-04-17 14:30:41 AEST
4 years with no update = no bug
Comment 3 Damien Miller 2016-08-02 10:40:38 AEST
Close all resolved bugs after 7.3p1 release