Re: /bzr/squid3/trunk/ r12925: Bug 3297: Fix openSSL related build failures

On 07/01/2013 01:41 PM, Tsantilas Christos wrote:
> The problem looks that it is that is is uses an older version to
> configure openSSL which is installed under the "/usr/" and finally
> builds with a newer version which installed under the "/usr/local/"
>
> This is because it finds an other component under the "/usr/local" and
> include these locations to build squid.
>
> I believe that configuring using:
> ./configure --with-openssl=/usr/local/
> will fix the problem.
>
> We have also a "3.HEAD-amd64-FreeBSD-9.1" build which uses the gcc
> compiler. In configure.ac script I am seeing the following tests:
>
> if test "$squid_cv_compiler" = "gcc"; then
> case "$squid_host_os" in
> .....
> freebsd)
> # FreeBSD places local libraries and packages in /usr/local
> CFLAGS="$CFLAGS -I/usr/local/include"
> CXXFLAGS="$CXXFLAGS -I/usr/local/include"
> LDFLAGS="$LDFLAGS -L/usr/local/lib -Wl,-R/usr/local/lib"
> ;;
>
> We should include the "/usr/local/" include and library paths for clang
> compiler too.

The attached patch should fix this
It just add the "usr/local/*" paths for FreeBSD in all compilers. Looks
that the "-I", "-L" and "-Wl,-R" flags supported for both clang and gcc,
so for these compilers the patch should work well.
Are we supporting any other compiler in FreeBSD?