in reply to Re^2: Errors during "make test" of DBD::Sybase
in thread Errors during "make test" of DBD::Sybase

In t/main.t, change $DBI::err to $sth->err and see if that solves the problem.

We still have the weirdness that you don't get the message text, though.

Michael

  • Comment on Re^3: Errors during "make test" of DBD::Sybase

Replies are listed 'Best First'.
Re^4: Errors during "make test" of DBD::Sybase
by Bone_Scavenger (Novice) on Oct 19, 2004 at 16:13 UTC
    Sorry, was off all day Monday and Tuesday morning.

    You wanted me to do this, right?

    else { print "ok 7\n"; ($sth->err == 208) and print "ok 8\n" or print "not ok 8\n";

    Same result - "not ok 8"

      Michael had an offline discussion with someone from Sybase. They suggested that I try building the "firstapp" Open Client sample program and change the select to a non-existent table (to trigger a 208 error), to see if I get the msg text. I did that, and here's the output:
      Server message: number(5701) severity(10) state(2) line(0) Server name: SQLLAM01 Changed database context to 'master'. Server message: number(208) severity(16) state(1) line(1) Server name: SQLLAM01 pubs2..authors not found. Specify owner.objectname or use sp_h +elp to check whether the object exists (sp_help may produce l.
      Since I see the message text, I'm guessing that my Open Client installation is working fine. Does that mean it's a Perl or DBI::Sybase problem?

      Thanks.

        We finally (after much searching) found the problem.

        DBD::Sybase detects that it is being built in a 64bit mode, and in that situation adds -DSYB_LP64 to the compile line. This is needed to get proper 64bit mode for Sybase's libraries and include files - except on Tru-64/OSF-1/Dec Unix!

        Removing the -DSYB_LP64 fixes the problem. I'll add the appropriate change to the Makefile.PL for the next release.

        Michael