many other interestingly-named functions are exported too: nm -D /usr/lib*/libmysqlclient.so | grep ' T ' | grep -v my list_free(), however, conflicts with dev-libs/liblist. Thus a program may not work if it links against both libmysqlclient and liblist and tries to use liblist's API.
Err, why is this a gentoo bug? I'm going to resolve this as UPSTREAM. Please reopen it only if you are sure that it has to do with us. If you reopen, please, also paste your emerge --info output, and the affected mysql versions if not all. Thank you for your report.
(In reply to comment #1) > Err, why is this a gentoo bug? I'm going to resolve this as UPSTREAM. I tried going upstream but their bugtracker refuses to let me in even after I tried to register and everything. I think this is a gentoo bug because dev-libs/liblist is in portage. I only have dev-db/mysql-5.0.84-r1 installed atm, I'll be working on updating my system... and I hope you'd be able to easily test if the latest unstable/stable has the bug by using the ``nm'' command I gave you ;-).
Created attachment 227137 [details] emerge--info.txt
http://bugs.mysql.com/report.php let me in today :-).
I was wondering about the shared lib patch, but I noticed the following on mysql-5.1 (for which we still don't have the shared lib patch yet). 0000000000032970 T list_add 0000000000032a80 T list_cons 00000000000329b0 T list_delete 0000000000032ae0 T list_free 0000000000032a20 T list_length 00000000000329f0 T list_reverse 0000000000032a40 T list_walk
This still applies to mariadb-5.2.9, mysql-5.1.59 and mysql-5.5.17. Upstream bug was closed for not getting the requested feedback.
No progress on upstream bug. A quick testing seems to confirm this is still present on mariadb-5.2.12-r1 and mysql-5.1.62-r1.
(In reply to comment #7) > No progress on upstream bug. > A quick testing seems to confirm this is still present on mariadb-5.2.12-r1 > and mysql-5.1.62-r1. It also seems to affect mariadb-5.5.25-r1, so I suspect it's also present on mysql-5.5* (will test later)
(In reply to comment #8) > (In reply to comment #7) > > No progress on upstream bug. > > A quick testing seems to confirm this is still present on mariadb-5.2.12-r1 > > and mysql-5.1.62-r1. > > It also seems to affect mariadb-5.5.25-r1, so I suspect it's also present on > mysql-5.5* (will test later) I've just confirmed this still affects both mariadb-5.5.30 and mysql-5.5.30. Unfortunately, the upstream bug was closed on 2010 and there has been no activity since, so I don't think there's anything we can do.
(In reply to Jorge Manuel B. S. Vicetto from comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > No progress on upstream bug. > > > A quick testing seems to confirm this is still present on mariadb-5.2.12-r1 > > > and mysql-5.1.62-r1. > > > > It also seems to affect mariadb-5.5.25-r1, so I suspect it's also present on > > mysql-5.5* (will test later) > > I've just confirmed this still affects both mariadb-5.5.30 and mysql-5.5.30. > Unfortunately, the upstream bug was closed on 2010 and there has been no > activity since, so I don't think there's anything we can do. I've confirmed it still affects mariadb-5.5.32 and mysql-5.5.32. The upstream bug is still closed and had no more activity. @Robin: another CANTFIX?
I'm going to close this as UPSTREAM as this needs to be fixed by upstream.
