Re: Hello Word\n

In addition to almut's and moritz's reply, you need to remember that the DBlib.so has dependencies on Sybase's client libraries (libsybdb I think). So ... even if the two machines were the same architecture, you would need to copy way more than DBlib.so.

Even if you copy over libsybdb, there may be many other library dependencies (and/or incompatibilities) you need to worry about. Installing via cpan is your best option. Also, why DBlib? Is there a reason for not using DBD::Sybase?

-derby

update: As JavaFan says, this is really a deployment issue. If you have that many servers, it's easier to build on one server (or one server of each architecture type) and then use something like rsync or rdist to deploy.

Comment on Re: Hello Word\n

Replies are listed 'Best First'.
Re^2: Sybase::DBlib probs\n by wilko (Acolyte) on Nov 20, 2008 at 13:31 UTC
Thanks derby. i have not looked at DBD::Sybase. Is this better in some way than DBlib? I'm pretty new to the perl world so kinda stumbled into using DBlib. I will have a look...rgds	[reply]
Re^3: Sybase::DBlib probs\n by derby (Abbot) on Nov 20, 2008 at 14:19 UTC
Yes. I believe DBD::Sybase is the better way to go. Sybase::DBLib is based on the older version of the Sybase client library (DBLib) -- older as in DBLib is from the 80's and the newer CTLib is from the 90's. There's always rumblings that Sybase is going to discontinue DBLib (but that never appears to actually occur). You can decide for yourself which c-based lib you want to use by checking out the faq. Your choice of which c-based lib you want to use will influence which perl modules you want/need to use. That all being said, DBD::Sybase is the more active module (it's been a few years since Sybase::DBLib has been updated). As with all things perl/sybase, if mpeppler chimes in, takes his advice -- he's the maintainer of most (all?) things sybase/perl. (Also, if jfroebe chimes in, take his advice too -- he's very deeply involved with sybase). -derby	[reply]