in reply to DBD::mysql installation

Anonymous Monk,
I have. I followed the instructions that bart was kind enough to point out to me. I only encountered one problem with incompatible types in a couple of header files. If you follow these instructions and you run into the same problem, let me know and I will re-figure out how I got around them.

Cheers - L~R

Replies are listed 'Best First'.
Re^2: DBD::mysql installation
by Anonymous Monk on Apr 07, 2005 at 12:42 UTC
    Thanks, but these are the same instructions I have been following without success. Like I said in a prior post, for some reason it doesn't seem to be finding the mysqlclient.lib file. Any other ideas?
      Anonymous Monk,
      Maybe - came to me as I was waking up this morning. I remember a handful of minor annoyances when I tried following those instructions to include the header file. As it turned out, I had installed MySQL server (Windows version) and it comes with its own client libraries. The wrong client libraries (Windows) were in the path prior to the Cygwin.

      Your comment concerning the mysqlclient.lib troubles me. It shouldn't be looking for a .lib extension. Are you sure you are pointing to the Cygwin built client library? Believe it or not, the Windows MySQL Server installation comes with shell scripts. If the perl Makefile.PL finds that script instead of the Cygwin client script, it will assume the wrong configuration information. It took me a while to find this.

      Cheers - L~R

        Well, I don't see any other mysql libraries except the ones that came with MySQL. I looked for them in the Cygwin installation tool, but didn't see any. As for the .lib file, that's just what I assumed looking at the option that failed. (-lmysqlclient). I do have the libmysql.dll, libmysql.lib, etc. in the path. As for the script you're talking about, I'm guessing that's the mysql_config script? If so, I found it, and I placed it in the same directory as the makefile.PL file. It wouldn't find it before. I also tried to edit this to make sure that the paths were correct because in that script, all of the paths were UNIX paths.