Tim Bunce writes: > On Fri, Jan 25, 2002 at 10:20:38AM +0100, H.Merijn Brand wrote: > > > > Now what would be a solution for a problem stated either here or on another > > group related to new perl builds and the use of DBI/DBD. Sybase (I think) only > > ships their new products with 64bit libraries, which have - of course - to be > > linked against a 64bit application, like perl built with -Duse64bitall. This > > is no problem for DBI, but what if this user wants both Sybase/64 *and* Unify > > (unlikely, I know, but there are probably better examples to be thought of) a > > database that (so far) only supports 32bit (static) builds and thus requires a > > 32bit perl. > > > > Is this something to put to p5p? > > Either it'll work or it won't. Probably not a p5p issue, more likely need > to ensure that other modules, like DBD::Sybase build okay with a perl built > with -Duse64bitall. But I'm just guessing.
A couple of things: First, although Sybase does ship the libraries in 64 bit mode there should normally also be a 32 bit version on the CD. Second - DBD::Sybase 0.94 won't build in 64 bit mode. However, try 0.94_01, which you can get from http://www.peppler.org/downloads, where I've applied the same fixes that enable sybperl (i.e. Sybase::CTlib and friends) to build in 64bit mode. Specifically Sybase has named all the 64bit libraries libxxx64.so, so the list of libraries need to be fixed, and a new -D flag needs to be included during the compile. Michael -- Michael Peppler - Data Migrations Inc. - http://www.mbay.net/~mpeppler [EMAIL PROTECTED] - [EMAIL PROTECTED] International Sybase User Group - http://www.isug.com
