Re: squid master build with alternate openssl fails

On 5/8/20 10:12 AM, Christos Tsantilas wrote:

> Squid master 699ade2d fails to build with an alternate OpenSsl, when the
> "--with-openssl=/path/to/openssl" is used.

Francesco, builds with custom OpenSSL paths are not that uncommon,
especially among SslBump admins. Would you be able to test that kind of
configuration in one of the Jenkins tests? It can be even combined with
other custom-path tests. Or is this too custom/special to warrant an
automated test in your opinion?


> I think that the issue added with the commit 245314010.

I speculate that the bug is related to the disappearance of the
LIBOPENSSL_PATH assignment in that commit. We still use that variable,
but we no longer set it.


Amos, would you be able to fix this?

Thank you,

Alex.



> Example build output:
> g++ -DHAVE_CONFIG_H
> -DDEFAULT_CONFIG_FILE=\"/usr/local/squid3-cvs/etc/squid.conf\"
> -DDEFAULT_SQUID_DATA_DIR=\"/usr/local/squid3-cvs/share\"
> -DDEFAULT_SQUID_CONFIG_DIR=\"/usr/local/squid3-cvs/etc\"   -I..
> -I../include -I../lib -I../src -I../include    -I../src
> -I/usr/include/libxml2 -Wall -Wpointer-arith -Wwrite-strings -Wcomments
> -Wshadow -Woverloaded-virtual -Werror -pipe -D_REENTRANT
> -I/usr/include/libxml2 -m64    -I/usr/include/p11-kit-1  -g -O2
> -march=native -MT CacheDigest.o -MD -MP -MF $depbase.Tpo -c -o
> CacheDigest.o CacheDigest.cc &&\
> mv -f $depbase.Tpo $depbase.Po
> In file included from cache_cf.cc:3427:0:
> cf_parser.cci: In function ‘int parse_line(char*)’:
> cf_parser.cci:1466:20: error: ‘Ssl’ has not been declared
>          parse_eol(&Ssl::TheConfig.ssl_crtd);
> ...
> 
> 
> My understanding is that squid enables ssl-crtd build (--with-ssl-crtd
> is given) but fails to detect OpenSsl correctly.
_______________________________________________
squid-dev mailing list
[email protected]
http://lists.squid-cache.org/listinfo/squid-dev