Skip Menu |

This queue is for tickets about the DBD-mysql CPAN distribution.

Report information
The Basics
Id: 83488
Status: rejected
Priority: 0/
Queue: DBD-mysql

Owner: Nobody in particular
Requestors: sveta.smirnova [...]

Bug Information
Severity: Normal
Broken in: 4.007
Fixed in: (no value)

Subject: Link unresolved external symbol __dosmaperr Visual Studio 2003
Download (untitled) / with headers
text/plain 1.1k
Originally reported by Godofredo Miguel Solorzano at Description: Compiling the package: DBD-mysql-4.007.tar.gz and creating the makefile with: perl.exe Makefile.PL --cflags="-I C:/DBS/mysql-5.0/include" --libs="-L C:/DBS/mysql-5.0/libmysql/release -lmysqlclient -lz -lm -lcrypt -lnsl" got the below link error: Creating library blib\arch\auto\DBD\mysql\mysql.lib and object blib\arch\auto\DBD\mysql\mysql.exp qlclient.lib(my_open.obj) : error LNK2019: unresolved external symbol __dosmaperr referenced in function _my_sopen b\arch\auto\DBD\mysql\mysql.dll : fatal error LNK1120: 1 unresolved externals KE : fatal error U1077: 'C:\Perl\bin\perl.exe' : return code '0x1' This link problem *only* happens when compiling the DBD::mysql with the compiler VS2003 and not happens with compiler VS2005. The Makefile was generated with the below command: perl.exe Makefile.PL --cflags="-I C:/dbs/mysql-5.0/include" --libs="-L C:/dbs/mysql-5.0/libmysql/release -lmysqlclient -lz -lm -lcrypt -lnsl" So this could be a compiler bug and not a mysqlclient.lib bug. For additional details see original bug report.
Download (untitled) / with headers
text/plain 457b
Closing ticket. I can't contact the reporter; I see no compelling reason to go back and fix stuff for MS Visual Studio 2003; and I can't replicate this bug because the compiler is no longer available from Microsoft. I have access to MSVC6 and some newer versions but not this old one. If there is someone who would have a valid case for needing Visual Studio 2003 that can provide a patch, they are welcome to submit them and I'm sure they'd be considered!

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to