On 05/18/2013 02:45 PM, Amos Jeffries wrote: > 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
Thank you. This is what happens: 1) configure script test for openSSL library. It uses the standard FreeBSD openSSL library installed under the "/usr/" directory 2) In later step decide that the CXXFLAGS will include the "-I/usr/local/include". Squid will compile with this option. 3) Under the "/usr/local/include" there is a new openSSL version 4) Because we configure the squid using the system openSSL library we are failing to compile. This is may happen for many reasons: because we have give "--prefix=/usr/local" and autoconf decides to include this directory in includes search path or because ANY of the other libraries used are installed under the "/usr/local" directory (eg the cpp_unit in our case) I thing there are not a lot of options: 1) configure with "--with-openssl=/usr/local" or 2) remove the openssl version installed under the "/usr/local" directory. opinions?
