Details
Major
Description
I presume it might be a problem for some other modern version, but I'm currently experiencing it on openSUSE 13.1
cmake . -DCMAKE_BUILD_TYPE=Debug && make
...
[ 18%] Building CXX object storage/innobase/CMakeFiles/innobase.dir/row/row0log.cc.o
/home/elenst/repo/10.0/storage/innobase/row/row0log.cc: In function 'dberr_t row_log_table_apply_ops(que_thr_t*, row_merge_dup_t*)':
/home/elenst/repo/10.0/storage/innobase/row/row0log.cc:2201:11: error: 'srv_buf_size' was not declared in this scope
ofs, srv_buf_size);
^
/home/elenst/repo/10.0/storage/innobase/row/row0log.cc: In function 'dberr_t row_log_apply_ops(trx_t*, dict_index_t*, row_merge_dup_t*)':
/home/elenst/repo/10.0/storage/innobase/row/row0log.cc:2988:11: error: 'srv_buf_size' was not declared in this scope
ofs, srv_buf_size);
^
make[2]: *** [storage/innobase/CMakeFiles/innobase.dir/row/row0log.cc.o] Error 1
make[1]: *** [storage/innobase/CMakeFiles/innobase.dir/all] Error 2
make: *** [all] Error 2
I found the bug http://bugs.mysql.com/bug.php?id=70047 which looks similar; but it's still in "verified" state, and MySQL 5.6 builds on the same openSUSE machine, so I'm not sure whether it's quite the same (or, maybe the bug just didn't get updated).
In any case, it would be good to make sure that the fix is either coming with the next InnoDB merge, or with "5.6 bugfixes" merge, or separately as a patch.
Gliffy Diagrams
Attachments
Issue Links
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
The workaround patch was taken from the following revision in mysql-server/5.6 and pushed into 10.0 tree:
------------------------------------------------------------
revno: 5400
revision-id: satya.bodapati@oracle.com-20130823123327-u7smqvlq9pwzzhjg
parent: mysql-builder@oracle.com-20130823114859-90gyn21dei3cm49q
committer: Satya Bodapati <satya.bodapati@oracle.com>
branch nick: mysql-5.6
timestamp: Fri 2013-08-23 18:03:27 +0530
message:
BUG#17316314 - SRV_BUF_SIZE NOT DECLARED
Temporary fix. Disabling FALLOC_FL_PUNCH_HOLE for now
------------------------------------------------------------
Apparently, the MySQL bug remains open because there is a plan for a real fix.