Compiling squid-3.3.5 with SSL on RedHat EL 6

[Chris Ross <cross@xxxxxxxxxxxxxxx>]

 I had gotten a patch for compiling with SSL on RHEL6 from the net, presumably by following something noted on this mailing list.  When 3.3.5 came out yesterday, and the change log noted that this issue had been addressed, I was pleased to upgrade to 3.3.5.

 However, with an unmodified tree, I seem to still be unable to compile certificate_db.cc on my x86_64 RedHat EL 6.3 host.  The following are the compilation errors:

g++ -DHAVE_CONFIG_H  -I../.. -I../../include -I../../lib -I../../src -I../../include   -I../../libltdl   -Wall -Wpointer-arith -Wwrite-strings -Wcomments -Werror -pipe -D_REENTRANT -g -O2 -std=c++0x -MT certificate_db.o -MD -MP -MF .deps/certificate_db.Tpo -c -o certificate_db.o certificate_db.cc
certificate_db.cc: In static member function ‘static void Ssl::CertificateDb::sq_TXT_DB_delete(TXT_DB*, const char**)’:
certificate_db.cc:170: error: invalid conversion from ‘void*’ to ‘const _STACK*’
certificate_db.cc:170: error:   initializing argument 1 of ‘void* sk_value(const _STACK*, int)’
certificate_db.cc: In member function ‘bool Ssl::CertificateDb::deleteInvalidCertificate()’:
certificate_db.cc:520: error: invalid conversion from ‘void*’ to ‘const _STACK*’
certificate_db.cc:520: error:   initializing argument 1 of ‘void* sk_value(const _STACK*, int)’
certificate_db.cc: In member function ‘bool Ssl::CertificateDb::deleteOldestCertificate()’:
certificate_db.cc:551: error: invalid conversion from ‘void*’ to ‘const _STACK*’
certificate_db.cc:551: error:   initializing argument 1 of ‘void* sk_value(const _STACK*, int)’
certificate_db.cc: In member function ‘bool Ssl::CertificateDb::deleteByHostname(const std::string&)’:
certificate_db.cc:568: error: invalid conversion from ‘void*’ to ‘const _STACK*’
certificate_db.cc:568: error:   initializing argument 1 of ‘void* sk_value(const _STACK*, int)’
make[3]: *** [certificate_db.o] Error 1


 Is anyone either in the core squid team, or in the user community, aware both of the short-coming of the fix for bug 3759, and a way to address the issue myself in the short term?

 Thanks…

                           - Chris