[Templates] problems with make test (Template-Toolkit-2.09/t/dbi.t)

[Adam Monsen]

(I apologize for the length of this email and the number of text 
snippets... I wasn't sure if mailman would allow attachments, so I just 
quoted everything inline)

I ran into the following errors with 'make test' for Template Toolkit 
2.09 (yes I /did/ want to run the DBI tests):

------------------------8<------------------------
t/dbi............Use of uninitialized value in concatenation (.) or 
string at t/dbi.t line 64.
DBI connect() failed:

Please ensure that your database server is running and that you specified
the correct connection parameters.  If necessary, re-run the Makefile.PL
and specify new parameters, or answer 'n' when prompted:
  - Do you want to run the DBI tests?

FAILED 1:
t/dbi............FAILED test 1
        Failed 1/1 tests, 0.00% okay
------------------------>8------------------------
First off, the error message is much more verbose when this patch...
------------------------8<------------------------
*** Template-Toolkit-2.09/t/dbi.t.old   2003-06-23 19:45:35.000000000 -0700
--- Template-Toolkit-2.09/t/dbi.t       2003-06-23 19:45:41.000000000 -0700
***************
*** 62,68 ****
  if ($@ || ! $dbh) {
      warn <<EOF;
! DBI connect() failed:
      $DBI::errstr
  Please ensure that your database server is running and that you specified
--- 62,68 ----
  if ($@ || ! $dbh) {
      warn <<EOF;
! DBI connect() failed: $@
      $DBI::errstr
  Please ensure that your database server is running and that you specified
------------------------>8------------------------
...is applied:
------------------------8<------------------------
t/dbi............Use of uninitialized value in concatenation (.) or 
string at t/dbi.t line 64.
DBI connect() failed: install_driver(mysql) failed: Can't load 
'/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/DBD/mysql/mysql.so' 
for module DBD::mysql: 
/usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi/auto/DBD/mysql/mysql.so: 
undefined symbol: mysql_ssl_set at 
/usr/lib/perl5/5.8.0/i386-linux-thread-multi/DynaLoader.pm line 229.
 at (eval 4) line 3
Compilation failed in require at (eval 4) line 3.
Perhaps a required shared library or dll isn't installed where expected
 at t/dbi.t line 60



Please ensure that your database server is running and that you specified
the correct connection parameters.  If necessary, re-run the Makefile.PL
and specify new parameters, or answer 'n' when prompted:
  - Do you want to run the DBI tests?

FAILED 1:
t/dbi............FAILED test 1
        Failed 1/1 tests, 0.00% okay
------------------------>8------------------------
I'm not sure what $DBI::errstr is supposed to contain, but I get a blank 
line.

I have no idea what the error message means... my mysql driver is 
working perfectly as far as I know. I'm able to 
connect/SELECT/INSERT/UPDATE/etc. via DBI just fine using a simple test 
script or DBI::Shell.

To add to the strangeness, if I run the dbi.t test explicitly, it 
_succeeds_...
------------------------8<------------------------
[EMAIL PROTECTED] Template-Toolkit-2.09]# /usr/bin/perl 
"-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 
'blib/arch')" t/dbi.t
t/dbi....ok 

All tests successful.
Files=1, Tests=63,  3 wallclock secs ( 0.94 cusr +  0.03 csys =  0.97 CPU)
------------------------>8------------------------
Any ideas what's going on here? Hope you like the 2-character patch.

I've installed Template Toolkit anyway and it appears to be working 
fine, just thought I'd let you know about the failing test.

Thank you, hope this helps!

--
Adam Monsen
*** Template-Toolkit-2.09/t/dbi.t.old   2003-06-23 19:45:35.000000000 -0700
--- Template-Toolkit-2.09/t/dbi.t       2003-06-23 19:52:32.000000000 -0700
***************
*** 62,68 ****
  
  if ($@ || ! $dbh) {
      warn <<EOF;
! DBI connect() failed:
      $DBI::errstr
  
  Please ensure that your database server is running and that you specified
--- 62,68 ----
  
  if ($@ || ! $dbh) {
      warn <<EOF;
! DBI connect() failed: $@
      $DBI::errstr
  
  Please ensure that your database server is running and that you specified