dbTalk Databases Forums  

Possible mistake in file `libmysqlclient.def'

mailing.database.mysql-plusplus mailing.database.mysql-plusplus


Discuss Possible mistake in file `libmysqlclient.def' in the mailing.database.mysql-plusplus forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
dengxy
 
Posts: n/a

Default Possible mistake in file `libmysqlclient.def' - 11-23-2005 , 10:26 AM







SSBmYWlsZWQgdG8gYnVpbGQgbXlzcWwrKyBhZ2FpbnN0IE15U1 FMIDUuMCBzaW5jZSBpdHMgcmVs
ZWFzZSANCndpdGggdGhlIGdpdmVuIE1ha2VmaWxlLm1pbmd3Li BXYXJyZW4gWWFuZyB0b2xkIG1l
IHRvIG1pZ3JhdGUgDQp0byBWQy4gQnV0IG5vdyBJIGZvdW5kIH RoYXQgaXQgbWlnaHQgYmUgYW4g
aW5jb21wYXRpYmxlIGluIGZpbGUgDQpsaWJteXNxbGNsaWVudC 5kZWYgYWdhaW5zdCBNeVNRTCB2
ZXIgNS4wLiBCeSBkZWZhdWx0LCBJdCB3aWxsIA0KZW1pdCBhbi BlcnJvciBmb3IgYW4gdW5yZXNv
bHZlIGV4dGVybmFsIHN5bWJvbCBuYW1lZDoNCg0KbXlzcWxfbW 9yZV9yZXN1bHRzQDQNCm15c3Fs
X25leHRfcmVzdWx0QDQNCg0Kd2hlbiBidWlsZGluZyBleGFtcG xlcy4gSG93ZXZlciwgbGlibXlz
cWxjbGllbnQuZGVmIGNvbnRhaW5zOg0KDQouLi4NCm15c3FsX2 1vcmVfcmVzdWx0cw0KbXlzcWxf
bmV4dF9yZXN1bHQNCi4uLg0KDQpBZnRlciBjaGFuZ2VzIHRoZX NlIDIgbGluZXMgdG8gdGhlIHZl
cnNpb24gYWJvdmUoYXBwZW5kICJANCIpLCB0aGUgZXhhbXBsZX MgY2FuIGJlIGJ1aWx0IHN1Y2Nl
c3NmdWxseS4gSXMgdGhpcyBzdHJhbmdlPyBTaW5jZSANCnRoZS BvcmlnaW5hbCBvbmUgY2FuIHVz
ZSB3aXRoIE15U1FMIDQuMSwgb3IgdGhlIC5kZWYgZmlsZSBuZW VkIA0KcGF0Y2hlZCBhZ2FpbnN0
IE15U1FMIDUuMD8=



Reply With Quote
  #2  
Old   
Warren Young
 
Posts: n/a

Default Re: Possible mistake in file `libmysqlclient.def' - 11-23-2005 , 01:57 PM






dengxy wrote:
Quote:
emit an error for an unresolve external symbol named:

mysql_more_results@4
mysql_next_result@4

when building examples. However, libmysqlclient.def contains:

...
mysql_more_results
mysql_next_result
...

After changes these 2 lines to the version above(append "@4"), the examples can be built successfully. Is this strange? Since
the original one can use with MySQL 4.1, or the .def file need
patched against MySQL 5.0?
The lines without @X (where X is some number) are all technically
mistakes. We add the proper @X value whenever we need it. You are
simply discovering a new case where another @X is needed.

You may want to join with "Death Gauge" in his thread to get MySQL++
working with MinGW. He is already working on this sort of problem.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw



Reply With Quote
  #3  
Old   
Warren Young
 
Posts: n/a

Default Re: Possible mistake in file `libmysqlclient.def' - 11-28-2005 , 04:04 PM



dengxy wrote:
Quote:
ver 2.0.7 has been shipped
without patched and consequently cannot compile with MinGW by
default.
I know. That's because changing the DEF file is an incomplete fix.
Therefore, I'm not applying the patch yet. Come to me with a complete fix.

Quote:
BTW, please delete the thread with the ghostly backslash I didn't
typed indeed.
This is a mailing list. Nobody can delete or change posts.

--
MySQL++ Mailing List
For list archives: http://lists.mysql.com/plusplus
To unsubscribe: http://lists.mysql.com/plusplus?unsu...ie.nctu.edu.tw



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.