Re: problems loading DBD::MySQL

--0016e68fd02cc21329047af1f52a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

OK
boy is my face red! It was a port issue! MySQL defaults to 3306 and my
machine was stepping on the port.
I did go back and check the version as you described and it is indeed loade=
d
(v4.013) even though PPM says its not there. Afterwards I went to the effor=
t
of cleaning the makefile and starting over with the makefile.pl - this time
I explicitly called the libmysql.lib when I  compiled it - Next I ran the
'make test' only to see the same skips. At that point I jumped into the
mysql.mtest and specified the DB name, user and password. once I re-ran the
test it started connecting, but with 15 of 35 tests failing and 745 subtest
failing. I did build out a small test program and it connected with out
issue this time. Do I ignore the fails at this point, consider myself luck
and go on with my life?

btw: thanks for all the advice!

Keith

On Thu, Dec 17, 2009 at 7:36 AM, Selke, Gisbert W. <
[email protected]> wrote:

> Hi Keith --
>
> > -----Urspr=FCngliche Nachricht-----
> > Von: Keith Thomas [mailto:[email protected]]
> > Gesendet: Mittwoch, 16. Dezember 2009 21:47
>  my only question now is that when I go to the ppm repository
> > and look, it does not list DBD::mysql, but if I go to the
> > \Perl\site\lib\DBD\mysql I find a pod and pm file. Am I ok then?
> It's an old and unresolved issue that ppm will not pick up any manual
> installations. ppm is all very nice and handy where it works, but sometim=
es
> it doesn't, and you have to resort to other means (like you did). Then pp=
m
> will not know about this, but perl itself will: Try
> perl -MDBD::mysql -e "print $DBD::mysql::VERSION"
> The next glitch will come up when next time you will be using ppm in orde=
r
> to upgrade DBD::mysql (supposing you resolve the firewall problem). I gue=
ss
> one could write a "repair script" for the ppm database to update it about
> all the manual changes (probably someone already has one this -- I haven'=
t
> been concerned enough myself).
>
> If you're really concerned about it, there is still one way out:
> * make your DBD::mysql as described by you, but do not install
> * make ppm
> * Take the resulting ppm/ppd files and drop them into some directory that
> will serve as your local ppm repository
> * direct ppm (the programme) to your local repository instead of one of
> those on the internet
> * install
>
> \Gisbert
>

--0016e68fd02cc21329047af1f52a--