I have noticed that RedHat 7+ does some weird things when it comes to
headers and libraries like make extra directories or replace some well known
ones.
It might be that you installed the MySQL headers to /usr/local/include and
RedHat does not look there. I have hit that problem with Mandrake too. To
fix, find the mysql.h and subsidiary files, then 'ln -s' them (or the entire
directory) to /usr/include. If you have trouble with the libraries, just add
them to the /etc/ld.so.conf file and then run ldconfig.
Hope it helps a little. Wish ya luck man!
========================
Mike Duncan
Web Master/Developer
Sonopress LLC
828.658.6082 (Desk)
828.423.3310 (Cell)
[EMAIL PROTECTED]
[EMAIL PROTECTED]
========================
-----Original Message-----
From: Stefan Antonowicz [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 3:27 PM
To: Hardy Merrill
Cc: [EMAIL PROTECTED]
Subject: RE: Problems running DBD::mysql
Thanks, Hardy. I think you found a piece to my puzzle.
The DBI bundle nets me:
****
cpan> install Bundle::DBI
CPAN: Storable loaded ok
Going to read /root/.cpan/Metadata
Storable is up to date.
Net::Daemon is up to date.
RPC::PlServer is up to date.
Getopt::Long is up to date.
DBI is up to date.
*****
BUT, the DBD nets me:
*****
cpan> install DBD::mysql
Running install for module DBD::mysql
Running make for J/JW/JWIED/DBD-mysql-2.0901.tar.gz
Scanning cache /root/.cpan/build for sizes
CPAN: MD5 loaded ok
DBD-mysql-2.0901/....
<snip>
DBD-mysql-2.0901/constants.h
Removing previously used /root/.cpan/build/DBD-mysql-2.0901
CPAN.pm: Going to build J/JW/JWIED/DBD-mysql-2.0901.tar.gz
This is an experimental version of DBD::mysql. For production environments
you should prefer the Msql-Mysql-modules.
I will use the following settings for compiling and testing:
testpassword (default) =
testhost (default) =
testuser (default) =
nocatchstderr (default) = 0
testdb (default) = test
To change these settings, see 'perl Makefile.PL --help' and 'perldoc
INSTALL'.
Checking if your kit is complete...
Looks good
Using DBI 1.18 installed in
/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/auto/DBI
Writing Makefile for DBD::mysql
cp lib/DBD/mysql.pod blib/lib/DBD/mysql.pod
cp lib/DBD/mysql/INSTALL.pod blib/lib/DBD/mysql/INSTALL.pod
cp lib/DBD/mysql.pm blib/lib/DBD/mysql.pm
cp lib/Bundle/DBD/mysql.pm blib/lib/Bundle/DBD/mysql.pm
cp lib/Mysql/Statement.pm blib/lib/Mysql/Statement.pm
cp lib/Mysql.pm blib/lib/Mysql.pm
cc -c -I/usr/local/lib/perl5/site_perl/5.6.1/i686-linux/auto/DBI -fno-stric
t-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -
O2 -DVERSION=\"2.0901\" -DXS_VERSION=\"2.0901\" -fpic -I/usr/local/lib/per
l5/5.6.1/i686-linux/CORE dbdimp.c
In file included from dbdimp.c:29:
dbdimp.h:31:49: mysql.h: No such file or directory
dbdimp.h:32:49: errmsg.h: No such file or directory
make: *** [dbdimp.o] Error 1
/usr/bin/make -- NOT OK
Running make test
Can't test without successful make
Running make install
make had returned bad status, install seems impossible
**********
So the DBD::mysql install fails. I have two follow-up questions on that:
1) Why does the driver show up when I do:
perl -MDBI -e 'print join("\n",DBI->available_drivers) . "\n";
2) Has anyone encountered this type of failure before and, if so, do you
know the solution to the problem?
/s
-----Original Message-----
From: Hardy Merrill [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 25, 2001 3:01 PM
To: Stefan Antonowicz
Cc: Sterin, Ilya; [EMAIL PROTECTED]
Subject: Re: Problems running DBD::mysql
One thing you didn't mention is rebuilding DBI - try rebuilding DBI and
*then* rebuilding DBD::mysql. I prefer using CPAN, as I think you
said as well:
CPAN> install Bundle::DBI
CPAN> install DBD::mysql
It's been a while since I installed DBD::mysql, but I think(?) that
will work for DBD::mysql.
HTH.
--
Hardy Merrill
Mission Critical Linux, Inc.
http://www.missioncriticallinux.com
S