This is my first time using anything to do with Perl. I've installed several modules with no problem, but now I'm trying to install the Msql-Mysql-modules and the DBD::Mysql module keeps giving me errors. If anyone has experience with this or thoughts I'd appreciate some help! The server is running CentOS, Apache 1.3.3 and Direct Admin.

Creating files for MySQL ....................
WARNING: CAPI is not a known parameter.
WARNING: PL_FILES takes a hash reference not a array reference.
Please inform the author.
Checking if your kit is complete...
Looks good
Note (probably harmless): No library found for -lmysqlclient
Note (probably harmless): No library found for -lgz
Note (probably harmless): No library found for -lgcc
*** Warning: Path separator characters (`s') in the current directory path (/root/Msql-Mysql-modules-1.2219/mysql) may cause problems

Using DBI 1.48 (for perl 5.008 on i386-linux-thread-multi) installed in /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi/auto/DBI/
Writing Makefile for DBD::mysql
Writing Makefile for Msql-Mysql-modules
[root@mater Msql-Mysql-modules-1.2219]# make
Makefile:75: *** missing separator. Stop.

The configuration setup isn't finding your gzip, mysql and gcc libraries (a bit of a problem for building DBI::MySQL!). This could be cos your PATH variable is screwed (the first error looks that way) or because of some linking problem. Assuming that the OS is some *NIX variant I would guess that there is a problem with the libtool - did you install mysql et al yourself and if so did you run ldconfig (or system equivilent) afterwards?

Hiya,

I've experienced this one myself - take a look on Google.

http://www.google.co.uk/search?hl=en&q=%22WARNING%3A+PL_FILES+takes+a+hash+reference+%2 2&btnG=Search&meta=

Good Luck!

Joe

The DBI is installed already I think. It's the DBD::Mysql that I'm struggling with.

I didn't install mysql myself, it came on the server. Now I suspect that this may be a problem as you say because the server does have Direct Admin installed for managing users/domains etc. and so I think it may have played around with the sql database layout too....

It is running on CentOS which is a *nix variant. Hmmm maybe I should post this question on the Direct Admin boards if it is indeed messing things up.

Haha figured it out with some help searching the DA boards. For anyone interested RH9 which CentOS is based on has a buggy problem and this needs to be added/fixed before running a make

export LANG=C

If the base DBI module built happily then it is almost certainly a libraries problem - the 'probably harmless' notes look very harmfull to me!

You beat me to it....

Was just going to ask if the OS was Red Hat based, 'cos it has issues!

Joe