Please excuse the cross-posting, but I have a real problem and have no
idea what to do.
This morning, I had to install a new version of perl on a
very-soon-to-be-production box because of a bug in the then-installed
version (5.005_02). After installing perl 5.005_03 on the box, I can't
access any mSQL databases on the box (although I can from outside of the
box).
I have read through the past two years of messages from the listserve and
found a number that talk about these error messages. Unfortunately, none
of them are relevant (or at the solutions contained therein don't work in
this situation).
What I get when I run 'make test' on Msql-Mysql-modules-1.2202 (using
option #2 - msql only) is:
PERL_DL_NONLAZY=1 /usr/bin/perl -I../blib/arch -I../blib/lib
-I/opt/perl/lib/5.00503/sun4-solaris -I/opt/perl/lib/5.00503 -e 'use
Test::Harness qw(&runtests $verbose); $verbose=0; runtests @ARGV;' t/*.t
t/00base............ok
t/10dsnlist.........
Config Error : Unknown section 'general' or element 'db_dir' at line 22
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 1-3
Failed 3/3 tests, 0.00% okay
t/20createdrop......
Config Error : Unknown section 'general' or element 'db_dir' at line 22
dubious
Test returned status 1 (wstat 256, 0x100)
DIED. FAILED tests 1-5
Failed 5/5 tests, 0.00% okay
t/30insertfetch.....
Config Error : Unknown section 'general' or element 'db_dir' at line 22
dubious
<Rest of output cut - you get the general idea>
*****************************************************************************
If I comment out the db_dir value in the msql.conf file, then I get the
same message with a minor variation - it croaks on the remote_access
definition:
"Config Error : Unknown section 'general' or element 'remote_access' at line 33"
*****************************************************************************
I know that a number of people (including Bambi) have suggested relinking
the libmsql.a file into the perl modules. The thing is that I either
don't know how this is done or it doesn't work. I've done the following:
1) 'make'd, tested, and installed msql 2.0.10.1 from scratch
2) 'make'd, tested, and installed DBI-1.13 from scratch
3) 'make'd and installed Data-ShowTable-3.3 from scratch
4) 'make'd Msql-Mysql-modules-1.2202 from scratch
5) Ran 'make test' with the results above
6) Copied libmsql.a -> /usr/local/include and did 1-4 again
and I still get the same message. If you don't do the relinking when you
run 'make' on Msql-Mysql-modules-1.2202, how DOES one relink. I tried
making the DB_Dir explicitly '/usr/local/Hughes/msqldb'. I made sure that
the 'test' database was created. I even tried going back to a previous
version of the modules (1.2010) and I still get the same message.
My current architecture is:
Sun Ultra2
Solaris 2.6
perl 5.005_03 for sun4-solaris
I've made everything from /usr/local/Hughes on down a) owned by msql and
given read/execute to everyone in all subdirectories under that directory.
Could this be a problem with perl 5.005_3? I set up dynamic linking, but
I wouldn't think that that would make a difference in the (gcc-based)
linking of the modules (although I tried recompiling perl 'static'ly and
everything else from scratch, AGAIN with the same results).
The thing is, my previous mSQL was 2-0.5 and the msql.conf has the
Remote_Access value in it and I never had a problem. This message started
coming up as soon as I tried to re-install the msql stuff after installing
the new perl.
Any help on what could be happening would be appreciated.
Stephen Westman
Electronic Services Librarian
University of Texas at San Antonio Library
6900 North Loop 1604 West
San Antonio, TX 78249
swestman@stripped
