I wrote:

> I'm trying to build DBD::mysql on Solaris 2.8; Perl 5.6.1.
> I did this before using an older version.  For this one I'm
> using DBD::mysql 2.1024; mysql version 3.23.55.  It builds
> fine, but when I run the tests I get this sort of error
> repeated for each one:
> 
> t/40nulls..........install_driver(mysql) failed: Can't load 
> 'blib/arch/auto/DBD/mysql/mysql.so' for module DBD::mysql: ld.so.1:
> /usr/local/bin/perl: fatal: relocation error: file
> blib/arch/auto/DBD/mysql/mysql.so: symbol mysql_real_escape_string:
> referenced symbol not found at
> /usr/local/lib/perl5/5.6.1/sun4-solaris/DynaLoader.pm line 206.
> at (eval 1) line 3
> Compilation failed in require at (eval 1) line 3.
> Perhaps a required shared library or dll isn't installed 
> where expected
>   at t/40nulls.t line 50
> t/40nulls..........dubious
>          Test returned status 255 (wstat 65280, 0xff00)
> DIED. FAILED tests 1-11
> 
> I found plenty of references to this using Google, but no fixes
> (none in English anyway).  I see the 'mysql_real_escape_string'
> in the mysqlclient lib being linked in.  The make settings it
> reports look like this:
> 
> I will use the following settings for compiling and testing:
> 
>    cflags        (mysql_config) = -I'/usr/local/mysql/include'
>    libs          (mysql_config) = 
> -L/usr/local/mysql/lib/mysql -lmysqlclient 
> -lcr
> ypt -lgen -lsocket -lnsl -lm
>    nocatchstderr (default     ) = 0
>    ssl           (guessed     ) = 0
>    testdb        (default     ) = test
>    testhost      (default     ) =
>    testpassword  (default     ) =
>    testuser      (default     ) =
> 
> Anyone know how to fix this?

I'm stumped here.  I went to the other box where I have this working.
Same versions of everything *except* that box is Solaris 2.8 and the
one where it's failing is 2.7 (I got that wrong above).  I compared all
lines in the make output and they're the same.  Same versions of gcc.
The working box had a slightly older version of MySQL.  I upgraded to
the same one and it still works.  I must have missed something ...
I found more references to this problem doing Google searches on a 
variety of platforms, but again no solutions ...  If anyone has any 
clues here let me know.

----
Steve Sapovits
GSI Commerce  http://wwww.gsicommerce.com
[EMAIL PROTECTED] 

Reply via email to