Re: Compile problem (was: MySQL Community Server 5.1.35 has been released)
Dave, do you really consider it helpful to do reply all to a release announcement, trying to send it to the announce and packagers list, including a full quote of the announcement text, and using the original subject line, when you are asking for help about a compile problem? Dave Shariff Yadallee - System Administrator a.k.a. The Root of the Problem wrote: [[...]] Error in compiling: mv -f .deps/liboptions_la-priv.Tpo .deps/liboptions_la-priv.Plo /bin/sh ../../libtool --preserve-dup-deps --tag=CXX --mode=link g++ -O3 -fno-implicit-templates -fno-exceptions -fno-rtti -DDEFAULT_PID_FILE_NAME=/usr/contrib/mysqld/mysqlmanager.pid -DDEFAULT_LOG_FILE_NAME=/usr/contrib/mysqld/mysqlmanager.log -DDEFAULT_SOCKET_FILE_NAME=/tmp/mysqlmanager.sock -DDEFAULT_PASSWORD_FILE_NAME=/etc/mysqlmanager.passwd -DDEFAULT_MYSQLD_PATH=/usr/contrib/libexec/mysqld -DDEFAULT_CONFIG_FILE=my.cnf -DPROTOCOL_VERSION=10 -O3 -fno-implicit-templates -fno-exceptions -fno-rtti -o liboptions.la liboptions_la-options.lo liboptions_la-priv.lo ../../libmysql/get_password.lo -lm test: unrecognized integer ` ar cru .libs/liboptions.a .libs/liboptions_la-options.o .libs/liboptions_la-priv.o ../../libmysql/.libs/get_password.o ~ranlib .libs/liboptions.a/liboption' ../../libtool: arith: syntax error: 47 + .libs/liboptions_la-options.o~RANLI gmake[2]: *** [liboptions.la] Error 2 gmake[2]: Leaving directory `/usr/src/contrib/mysql/mysql-5.1.35/server-tools/instance-manager' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/src/contrib/mysql/mysql-5.1.35/server-tools' gmake: *** [all-recursive] Error 1 *** Error code 2 Stop. Help!! I can't. I cannot even try to help you, if you do not provide the necessary information. All I can do is give you the corresponding line from my log, split into several lines for better readability: /bin/sh ../../libtool --preserve-dup-deps --tag=CXX --mode=link gcc -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused-function -Wunused-label -Wunused-value -Wunused-variable -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -mtune=native -O3 -fno-omit-frame-pointer -g -fno-implicit-templates -fno-exceptions -fno-rtti -DDEFAULT_PID_FILE_NAME=/usr/local/mysql/var/mysqlmanager.pid -DDEFAULT_LOG_FILE_NAME=/usr/local/mysql/var/mysqlmanager.log -DDEFAULT_SOCKET_FILE_NAME=/tmp/mysqlmanager.sock -DDEFAULT_PASSWORD_FILE_NAME=/etc/mysqlmanager.passwd -DDEFAULT_MYSQLD_PATH=/usr/local/mysql/libexec/mysqld -DDEFAULT_CONFIG_FILE=my.cnf -DPROTOCOL_VERSION=10 -Wimplicit -Wreturn-type -Wswitch -Wtrigraphs -Wcomment -W -Wchar-subscripts -Wformat -Wparentheses -Wsign-compare -Wwrite-strings -Wunused-function -Wunused-label -Wunused-value -Wunused-variable -Wreorder -Wctor-dtor-privacy -Wnon-virtual-dtor -felide-constructors -fno-exceptions -fno-rtti -mtune=native -O3 -fno-omit-frame-pointer -g -fno-implicit-templates -fno-exceptions -fno-rtti -rdynamic -o liboptions.la liboptions_la-options.lo liboptions_la-priv.lo ../../libmysql/get_password.lo -lpthread -lcrypt -lnsl -lm -lpthread This was running on Linux (SuSE 10.3) running on an Athlon, using libtool 1.5.24 and gcc 4.2.1. Looking at the text you quote, it seems the commands executed by libtool got garbled: A command starting with ar cru suddenly continues with ~ranlib which doesn't make any sense to me. I suspect some problem around your libtool installation, or with your file system (affecting some generated files). Jörg -- Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com (+49 30) 417 01 487 Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org
Re: MySQL Community Server 5.1.35 has been released
On Thu, Jun 04, 2009 at 01:27:34PM -0600, Timothy Smith wrote: Dear MySQL users, MySQL Community Server 5.1.35, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.35 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.35 on new servers or upgrading to MySQL 5.1.35 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-35.html Enjoy! Timothy Smith The MySQL build team at Sun Microsystems === This release of MySQL has two known outstanding issues for Windows: * The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security. (There is a checkbox that allows this on the security screen of the configuration wizard.) Then check your settings: + If the old root password and security settings are okay, you are done and can proceed to use MySQL. + Otherwise, reconfigure with the wizard and make any changes on the second configuration attempt. The wizard will properly prompt for the existing root password and allow changes to be made. This issue has been filed as Bug#45200: http://bugs.mysql.com/45200 for correction in a future release. * The Windows configuration wizard allows changes to InnoDB settings during a reconfiguration operation. For an upgrade, this may cause difficulties. To work around this, use one of the following alternatives: + Do not change InnoDB settings. + Copy files from the old InnoDB location to the new one. This issue has been filed as Bug#45201: http://bugs.mysql.com/45201 for correction in a future release. Bugs fixed: * Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319: http://bugs.mysql.com/319, Bug#38205: http://bugs.mysql.com/38205) See also Bug#43217: http://bugs.mysql.com/43217. * Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944: http://bugs.mysql.com/42944) * Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179: http://bugs.mysql.com/44179) * Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393: http://bugs.mysql.com/39393) * Replication: The following erors were not correctly reported: + Failures during slave thread initialization + Failures while initializing the relay log position (immediately following the starting of the slave thread) + Failures while processing queries passed through the --init_slave option. Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197: http://bugs.mysql.com/38197) * Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set
MySQL Community Server 5.1.35 has been released
Dear MySQL users, MySQL Community Server 5.1.35, a new version of the popular Open Source Database Management System, has been released. MySQL 5.1.35 is recommended for use on production systems. For an overview of what's new in MySQL 5.1, please see http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html For information on installing MySQL 5.1.35 on new servers or upgrading to MySQL 5.1.35 from previous MySQL releases, please see http://dev.mysql.com/doc/refman/5.1/en/installing.html MySQL Server is available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/ Not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing For information on open issues in MySQL 5.1, please see the errata list at http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html The following section lists the changes in the MySQL source code since the previous released version of MySQL 5.1. It may also be viewed online at http://dev.mysql.com/doc/refman/5.1/en/news-5-1-35.html Enjoy! Timothy Smith The MySQL build team at Sun Microsystems === This release of MySQL has two known outstanding issues for Windows: * The .msi installer does not detect an existing root password on the initial configuration attempt. To work around this, install and configure MySQL as normal, but skip any changes to security. (There is a checkbox that allows this on the security screen of the configuration wizard.) Then check your settings: + If the old root password and security settings are okay, you are done and can proceed to use MySQL. + Otherwise, reconfigure with the wizard and make any changes on the second configuration attempt. The wizard will properly prompt for the existing root password and allow changes to be made. This issue has been filed as Bug#45200: http://bugs.mysql.com/45200 for correction in a future release. * The Windows configuration wizard allows changes to InnoDB settings during a reconfiguration operation. For an upgrade, this may cause difficulties. To work around this, use one of the following alternatives: + Do not change InnoDB settings. + Copy files from the old InnoDB location to the new one. This issue has been filed as Bug#45201: http://bugs.mysql.com/45201 for correction in a future release. Bugs fixed: * Important Change: Replication: The transactional behavior of STOP SLAVE has changed. Formerly, it took effect immediately, even inside a transaction; now, it waits until the current replication event group (if any) has finished executing, or until the user issues a KILL QUERY or KILL CONNECTION statement. This was done in order to solve the problem encountered when replication was stopped while a nontransactional slave was replicating a transaction on the master. (It was impossible to roll back a mixed-engines transaction when one of the engines was nontransactional, which meant that the slave could not safely re-apply any transaction that had been interrupted by STOP SLAVE.) (Bug#319: http://bugs.mysql.com/319, Bug#38205: http://bugs.mysql.com/38205) See also Bug#43217: http://bugs.mysql.com/43217. * Partitioning: When a value was equal to a PARTITION ... VALUES LESS THAN (value) value other than MAXVALUE, the corresponding partition was not pruned. (Bug#42944: http://bugs.mysql.com/42944) * Replication: Unrelated errors occurring during the execution of RESET SLAVE could cause the slave to crash. (Bug#44179: http://bugs.mysql.com/44179) * Replication: The --slave-skip-errors option had no effect when using row-based logging format. (Bug#39393: http://bugs.mysql.com/39393) * Replication: The following erors were not correctly reported: + Failures during slave thread initialization + Failures while initializing the relay log position (immediately following the starting of the slave thread) + Failures while processing queries passed through the --init_slave option. Information about these types of failures can now be found in the output of SHOW SLAVE STATUS. (Bug#38197: http://bugs.mysql.com/38197) * Replication: Killing the thread executing a DDL statement, after it had finished its execution but before it had written the binlog event, caused the error code in the binlog event to be set (incorrectly) to ER_SERVER_SHUTDOWN or ER_QUERY_INTERRUPTED, which caused replication to fail. (Bug#37145: http://bugs.mysql.com/37145) See also
