Re: severe build bug 5.5 viossl

2013-06-09 Thread Claudio Nanni
Hi Nick,

It seems it is fixed already in MariaDB:
http://bugs.mysql.com/bug.php?id=68999

[9 Jun 9:34] Michael Widenius

This was fixed in MariaDB 5.5 in May 2013 as part of our merge of
MySQL 5.5 to MariaDB 5.5.

Cheers

Claudio


2013/6/9 Nick Edwards nick.z.edwa...@gmail.com

 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

 For list archive, patch is:


 --- mysql-5.5.32/vio/viossl.c   2013-05-17 01:47:14.0 +1000
 +++ mysql-5.5.32a/vio/viossl.c  2013-06-09 15:38:06.0 +1000
 @@ -172,8 +172,10 @@
SSL_SESSION_set_timeout(SSL_get_session(ssl), timeout);
SSL_set_fd(ssl, vio-sd);
  #ifndef HAVE_YASSL
 +#ifdef SSL_OP_NO_COMPRESSION
SSL_set_options(ssl, SSL_OP_NO_COMPRESSION);
  #endif
 +#endif

if ((r= connect_accept_func(ssl))  1)
{

 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/mysql




-- 
Claudio


Re: severe build bug 5.5 viossl

2013-06-09 Thread Nick Edwards
yes I'm aware, it is why I made the comment about change

However still subject to corporate policy which means sticking with
mysql until they screw up on regular basis, so if they fail to fix
this by next version, I can take it to CIO and present my case, two
deliberate broken versions when fix made available to them months ago,
should, get me a win to move away from mysql.  (perhaps this is what
oracle wants anyway, since mysql earns them no money)


On 6/9/13, Claudio Nanni claudio.na...@gmail.com wrote:
 Hi Nick,

 It seems it is fixed already in MariaDB:
 http://bugs.mysql.com/bug.php?id=68999

 [9 Jun 9:34] Michael Widenius

 This was fixed in MariaDB 5.5 in May 2013 as part of our merge of
 MySQL 5.5 to MariaDB 5.5.

 Cheers

 Claudio


 2013/6/9 Nick Edwards nick.z.edwa...@gmail.com

 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

 For list archive, patch is:


 --- mysql-5.5.32/vio/viossl.c   2013-05-17 01:47:14.0 +1000
 +++ mysql-5.5.32a/vio/viossl.c  2013-06-09 15:38:06.0 +1000
 @@ -172,8 +172,10 @@
SSL_SESSION_set_timeout(SSL_get_session(ssl), timeout);
SSL_set_fd(ssl, vio-sd);
  #ifndef HAVE_YASSL
 +#ifdef SSL_OP_NO_COMPRESSION
SSL_set_options(ssl, SSL_OP_NO_COMPRESSION);
  #endif
 +#endif

if ((r= connect_accept_func(ssl))  1)
{

 --
 MySQL General Mailing List
 For list archives: http://lists.mysql.com/mysql
 To unsubscribe:http://lists.mysql.com/mysql




 --
 Claudio


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql



severe build bug 5.5 viossl

2013-06-08 Thread Nick Edwards
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

For list archive, patch is:


--- mysql-5.5.32/vio/viossl.c   2013-05-17 01:47:14.0 +1000
+++ mysql-5.5.32a/vio/viossl.c  2013-06-09 15:38:06.0 +1000
@@ -172,8 +172,10 @@
   SSL_SESSION_set_timeout(SSL_get_session(ssl), timeout);
   SSL_set_fd(ssl, vio-sd);
 #ifndef HAVE_YASSL
+#ifdef SSL_OP_NO_COMPRESSION
   SSL_set_options(ssl, SSL_OP_NO_COMPRESSION);
 #endif
+#endif

   if ((r= connect_accept_func(ssl))  1)
   {

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql