On 18/05/2013 11:32 p.m., Tsantilas Christos wrote:
On 05/18/2013 02:01 PM, Amos Jeffries wrote:
On 18/05/2013 10:46 p.m., Tsantilas Christos wrote:
Hi all,
Looks that the new checks for enabling or not the openSSL hacks still
have some problems.
In this case I believe:
- The configure script checks with the openSSL version comes with
FreeBSD 9.0 release
- The squid compiled with the openSSL version which is installed under
the "/usr/local/" directory and probably is a newer release.
It is not clear to me why the -I/usr/local/include compiler option used
(I did not see any configure option related to this). I believe that if
the following configure command used:
./configure --with-openssl=/usr/local/
The build problem will gone.
Also if there is a way to see the config.log in this build will help...
http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-9.0-clang/ws/config.log
I have grabbed a copy for now in case the upcoming build 249 looses the
info you need.
This config.log include very little information....
My config.log have informations like:
configure:22042: result: yes
configure:22051: checking whether the workaround for SSL_get_certificate
works
configure:22083: g++ -o conftest -g -O2 -std=c++0x
-I/usr/local/src/openssl-1.0.1e/BUILD/include -I/usr/include/libxml2 -g
conftest.cpp -L/usr/local/src/openssl-1.0.1e/BUILD/lib -lssl -lcrypto
-lrt -ldl -ldl -Wl,-rpath -Wl,/usr/local/src/openssl-1.0.1e/BUILD/lib >&5
Does it require any spacial options to configure script to produce such
messages?
Ah. Doh. wrng log
There is also config.log in each btlayer-* directory from each layers build.
This seems to be the log from that failing maximus layer build:
http://build.squid-cache.org/job/3.HEAD-amd64-FreeBSD-9.0-clang/ws/btlayer-02-maximus/config.log
Amos
