FS#17214 - [mythtv] fails to run with mysql 5.1.41
Attached to Project:
Arch Linux
Opened by Matthew Gyurgyik (pyther) - Friday, 20 November 2009, 02:02 GMT
Last edited by Jürgen Hötzel (juergen) - Sunday, 06 December 2009, 20:46 GMT
Opened by Matthew Gyurgyik (pyther) - Friday, 20 November 2009, 02:02 GMT
Last edited by Jürgen Hötzel (juergen) - Sunday, 06 December 2009, 20:46 GMT
|
Details
Description: There is a C99 aliasing violation in the source
of Mysql 5.1.40 which causes client
errors (specifically with MythTV but probably also with others) when Mysql is compiled with -O3 optimization (GCC 4.4.2). http://bugs.mysql.com/bug.php?id=48284 Basically mythtv is rendered useless due to this bug. See this bbs thread: http://bbs.archlinux.org/viewtopic.php?id=85031 I have attached the patch to this bug report. It is a very simple patch which changes a char datatype to uchar datatype. Of course this is a upstream bug, but it would be nice to get fixed as many people use mythtv on arch. This may also fix other applications. The patch is extremely minimal (changes one character) in the code. |
This task depends upon
the patch builds the same, but there is a warning about casting to char **
i can verify this works correctly with mythtv.
it is store_param_type( (char **) &net->write_pos, param);
and should be store_param_type(&net->write_pos, param);
* Andrea
why is it its mythtv's fault?
this is confusing...
is built with
CFLAGS="-fPIC ${CFLAGS} -fno-strict-aliasing"
CXXFLAGS="-fPIC ${CXXFLAGS} -fno-strict-aliasing"
http://svn.mythtv.org/trac/ticket/6683 (Ticket that I was redirected to)
http://svn.mythtv.org/trac/ticket/7610 (The issue I created regarding the issue on arch)
http://mythtv.org/pipermail/mythtv-users/2009-November/271349.html (Continuation of MythTv Bug #7610)
mysql 5.1.41-3 may fix the problem at least according to the mysql bug report it should, but it seems like patching the code is a better solution. It isn't like the patch is huge or complex. Its simply changing the datatype of one variable.
havent tested 5.1.41-3, will do shortly.
Jürgen
Running MySQL package 5.1.41-3 & mythtv 0.22-3 and all is working here. Perhaps a revisit to ensure this really is still an issue.