ahh, i observe the same on solaris 10, but did not yet investigate -- the quicker way to solve this: just change the paths in config.status, let run config.status, and then compile :-)
regards, fritz Charles Diza thus spoketh: > > Wget 1.16.1 has broken detection of non-built-in openssl on MacOSX. > > Openssl comes with MacOSX but it's deprecated by Apple and it's an old > version. For this reason, many MacOSX users custom install a newer > openssl and put it in /usr/local/ssl (which, IIRC, is the default > location for custom openssl installs). > > Up through wget 1.16, the following configure flags sufficed to make > wget's configure script recognize this custom openssl and *use* it: > > ./configure --with-ssl=openssl --with-libssl-prefix=/usr/local/ssl > > But on wget 1.16.1, those same flags have no effect, and wget is built > against the Mac system openssl in /usr/lib, which is old and deprecated. > Something in the configure script must have changed. > > I hope that this is either repaired, or that the README/INSTALL are > amended to include special instructions on how to force wget to pick up > a custom openssl on MacOSX. > > I'm no programmer, but I have a hunch that the same batch of pkg-config > related changes (2014-11-01 in the ChangeLog) that broke pcre handling > on MacOSX (See earlier thread) have broken openssl detection. > > I do have pkg-config on my system, in /usr/local. I have found that > whether or not I remove pkg-config from my system, I can't get openssl > in /usr/local/ssl to get picked up and used to link with" lines. -- Friedrich Haubensak [email protected] | Science is true! Leibniz Institute for Age Research | Don't be mislead by facts. - Fritz Lipmann Institute - +----------------------------- Beutenbergstrasse 11, D-07745 Jena phone +49-3641-65-6202 | fax -6210 | http://www.fli-leibniz.de/
