ports/60302: MySQL client library should have version number bumped

Gordon Burditt gordonb at airmail.net
Tue Dec 16 17:00:29 UTC 2003


>Number:         60302
>Category:       ports
>Synopsis:       MySQL client library should have version number bumped
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 16 09:00:26 PST 2003
>Closed-Date:
>Last-Modified:
>Originator:     Gordon Burditt
>Release:        FreeBSD 4.9-STABLE i386
>Organization:
>Environment:
System: FreeBSD hammy.burditt.org 4.9-STABLE FreeBSD 4.9-STABLE #7: Sat Nov 22 14:13:11 CST 2003 gordon at hammy.burditt.org:/scratch5/i386-obj/usr/src/sys/HAMMY i386


	
	FreeBSD 4.9, Intel hardware, Upgrading from MySQL 4.1.0 to 4.1.1 server and client
>Description:
	
	I have encountered several applications linked with the MySQL 4.1.0 client
	(exim, mnogosearch, php, plus some of my own) library which exhibited 
	various problems (core dumping, messages from malloc() about the free list, 
	inability to connect to the server due to protocol problems) 
	after the client library was upgraded to 4.1.1.  So far, in all cases, 
	the problem was fixed by recompiling/relinking the application.
	Clients still using the 4.1.0 client library still work.
	Even older clients using various 3.* versions still work.

>How-To-Repeat:
	
	Link application against 4.1.0 libmysqlclient.so.14.  Replace library
	with 4.1.1 libmysqlclient.so.14 without relinking.  Test.  I can't 
	guarantee problems, but lots of applications had them.
>Fix:

	
	I suggest that the version number on the library should have been bumped,
	so that older applications continue to use the older library until they
	are recompiled.


>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list