I was using MySQL v5.0.51a (current community version is 5.0.51b). My
company just upgraded to Enterprise (v5.0.64) and we are seeing linking
problems with MySQL++ for zlib symbols. The specific problem is related
to this MySQL bug:
http://bugs.mysql.com/bug.php?id=34231&thanks=3¬ify=215
Here is the part of the MySQL++ build that fails:
gcc -shared coldata.lo connection.lo datetime.lo fields.lo
field_names.lo field_types.lo manip.lo myset.lo qparms.lo query.lo
result.lo row.lo sql_string.lo string_util.lo type_info.lo vallist.lo
-Wl,--whole-archive
/home/f5cm/cm/barnstormer/50487/f5_build/devfs/usr/lib/mysql/libz.a
/home/f5cm/cm/barnstormer/50487/f5_build/devfs/usr/lib/mysql/libmysqlcli
ent.a -Wl,--no-whole-archive -L/usr/lib -lssl
-L/home/f5cm/cm/barnstormer/50487/f5_build/devfs/usr/lib/mysql
-Wl,-soname -Wl,libmysqlpp.so.2 -o .libs/libmysqlpp.so.2.0.7
/home/f5cm/cm/barnstormer/50487/f5_build/devfs/usr/lib/mysql/libmysqlcli
ent.a(adler32.o)(.text+0x0): In function `adler32':
/home/f5cm/cm/barnstormer/50487/f5_build/BUILD/mysqlcom-5.0.64/zlib/adle
r32.c:61: multiple definition of `adler32'
/home/f5cm/cm/barnstormer/50487/f5_build/devfs/usr/lib/mysql/libz.a(adle
r32.o)(.text+0x0):/home/f5cm/cm/barnstormer/50487/f5_build/BUILD/mysqlco
m-5.0.64/zlib/adler32.c:61: first defined here
...
This is listed as a "Won't fix" on the MySQL site. In previous versions
the zlib definitions were not included in the libmysqlclient.a library.
Is this a known issue? Are there any patches available to get MySQL++
compiling again?
Thanks,
Kevin