Re: Re: cvs: php4 /ext/mysql/libmysql mega-patch

From: Date: Tue, 22 Aug 2000 18:09:21 +0000
Subject: Re: Re: cvs: php4 /ext/mysql/libmysql mega-patch
References: 1 2 3  Groups: php.dev php.dev 
Request: Send a blank email to php-dev+get-30232@lists.php.net to get a copy of this message
OK I copied the libmysql directory after the MySQL patches to a different directory and reverted to the old version. Once 4.0.2 is out we should update it. MySQL team - please don't commit next time unless you manage to fully build PHP :) It should pass the following: put php4 CVS in php4/ put Zend CVS in php4/Zend put TSRM CVS in php4/TSRM then in php4/ ./buildconf ./configure make That should easily build and it automatically builds with MySQL. php-dev - I think the CVS instructions on our site aren't quite accurate or at least the version I found wasn't. Does putting Zend and TSRM on the same directory level of php4/ still work? Andi At 04:10 PM 8/22/00 +0200, Sebastian Bergmann wrote:
Michael Widenius wrote: I have now update raid.h to the CVS tree. Okay, I now get no compilation errors, but lots of compiler warnings and these linker errors 
libmysql.lib(libmysql.obj)    : not resolved external symbol
                                _default_charset_info
libmysql.lib(mf_casecnv.obj) : not resolved external symbol 
                                _default_charset_info
libmysql.lib(libmysql.obj)    : not resolved external symbol
                                _get_charset
libmysql.lib(libmysql.obj)    : not resolved external symbol
                                _get_charset_by_name
libmysql.lib(libmysql.obj)    : not resolved external symbol
                                _charsets_dir
libmysql.lib(my_init.obj)     : not resolved external symbol
                                _free_charsets
libmysql.lib(my_compress.obj) : not resolved external symbol 
                                _compress
libmysql.lib(my_compress.obj) : not resolved external symbol 
                                _uncompress
It's just an update of the MySQL client interface to 3.23.23; There is no critical bugs out in the old code so you can delay this a bit if you want. Okay, who is able / responsible to revert / delay the MySQL's path? -- <?php $a=explode(" " ,"119 130 128 129 45 110 123 124 129 117 114 127 45 ". "125 117 125 45 117 110 112 120 114 127");for($i=0;$i<sizeof($a);$i++)print chr($a[$i]-13); /* http://sb.phpOpenTracker.de | sb@phpOpenTracker.de */ ?> -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net
--- Andi Gutmans <andi@zend.com> http://www.zend.com/

« previous php.dev (#30232) next »