Bug 5663

Summary:	undefined reference to `mysql_net__read__done_semaphore' when linking with libmysqlclient.a
Product:	Mageia	Reporter:	REINQUIN Franck <OLDTIMER.BUGZILLA>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	major
Priority:	Normal	CC:	dmorganec, guillomovitch
Version:	1	Keywords:	PATCH
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	mysql-5.5.23-1.mga1.src.rpm	CVE:
Status comment:

Description REINQUIN Franck 2012-04-28 22:54:41 CEST

Description of problem:
I'm rebuilding a homemade program which uses the libmysqlclient library. It used to build correctly with Mandriva 2010.2. Now I get the following messages :
/usr/lib64/libmysqlclient.a(net_serv.cc.o):(.probes+0x30): undefined reference to `mysql_net__write__start_semaphore'

A similar problem was spotted and corrected last year in Mandriva :
https://qa.mandriva.com/show_bug.cgi?id=62158

I have checked mysql.spec in the sources and there is indeed "-DENABLE_DTRACE=1" as mentioned in the aforementioned bug report.

I'm not familiar with rebuilding from sources through a spec file so I didn't go further. But I can try if needed.

Version-Release number of selected component (if applicable):
lib64mysql18-5.5.10-1.mga1 and lib64mysql18-5.5.23-1.mga1

How reproducible:
Other than with my own program, I don't know. Maybe amarok as it revealed the problem in the first place with Mandriva ? Not sure actually.

Steps to Reproduce:
1.
2.
3.

Comment 1 REINQUIN Franck 2012-04-28 23:33:13 CEST

(In reply to comment #0)
> I'm not familiar with rebuilding from sources through a spec file so I didn't
> go further. But I can try if needed.

Well, there is always a first time. I was unsatisfied to let it without trying more so I proceeded with a rebuild of mysql.

I have changed the spec file ("-DENABLE_DTRACE=1" to "-DENABLE_DTRACE=''", rebuilt mysql and replaced /usr/lib64/libmysqlclient.a with the new version : it works !

Manuel Hiebel 2012-04-29 00:40:43 CEST

Keywords: (none) => PATCH
CC: (none) => dmorganec, guillomovitch

Comment 2 Manuel Hiebel 2012-11-05 16:54:19 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Comment 3 Manuel Hiebel 2012-12-02 14:36:37 CET

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX