This was reported in 5.5.31, a patch, VERY SIMPLE was submitted.
The problem goes ignored by oracle
5.5.32 releases, same error, apply the same simple patch and builds
/tmp/mysql-5.5.32/vio/viossl.c: In function 'ssl_do': /tmp/mysql-5.5.32/vio/viossl.c:175: error: 'SSL_OP_NO_COMPRESSION' undeclared (first use in this function) /tmp/mysql-5.5.32/vio/viossl.c:175: error: (Each undeclared identifier is reported only once /tmp/mysql-5.5.32/vio/viossl.c:175: error: for each function it appears in.) make[2]: *** [vio/CMakeFiles/vio.dir/viossl.c.o] Error 1 make[1]: *** [vio/CMakeFiles/vio.dir/all] Error 2
Question, does anyone at oracle even bother with bug tracking now days? How can something that causes a fail of building with versions of openssl less then 1.0.0 go un fixed for so long.
Is this more proof that oracle DGAF about mysql? should I move to mariadb?
because if we have to re patch a failed build on 5.5.33, we will I think, since it shows oracle dont give a stuff
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
Jun 09
Claudio Nanni Re: severe build bug 5.5 viossl
Jun 09, 2013; 12:14
Claudio Nanni
Re: severe build bug 5.5 viossl
Jun 10
Nick Edwards Re: severe build bug 5.5 viossl
Jun 10, 2013; 09:02
Nick Edwards
Re: severe build bug 5.5 viossl
Search
Lasso Programming
This site manages and broadcasts several email lists pertaining to Lasso Programming and technologies related and used by Lasso developers. Sign up today!