Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Beatnik (493)

Beatnik
  (email not shown publicly)
http://www.ldl48.org/

A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.

Project Daddy of Spine [sf.net], a mod_perl based CMS.

In his superhero time (8.30 AM to 5.30 PM), he works on world peace.

Journal of Beatnik (493)

Wednesday February 22, 2006
12:41 PM

DBD::Sybase and Solaris

[ #28778 ]
I had some problems getting DBD::Sybase up and running on Solaris 9. I was using it in a CGI script on a proprietary framework and the environment variables seemed broken. I got the following error:

install_driver(Sybase) failed: Can't load '/usr/local/lib/perl5/site_perl/5.8.0/
sun4-solaris/auto/DBD/Sybase/Sybase.so' for module DBD::Sybase: ld.so.1:
perl: fatal: libgcc_s.so.1: open failed: No such file or directory at

I found libgcc_s.so.1 in my /usr/local/lib and that path was added to LD_LIBRARY_PATH. I tried recompiling with extra parameters, I tried setting the environment variable explicitly in the script but nothing seemed to work. I then looked back at my development setup (where it DID work) and found out that libgcc_s.so.1 was in /usr/lib on that machine. I quickly created a symlink and tata! It worked!

Small sidenote: If you're compiling DBD::Sybase for Netcool, don't forget to fetch the Netcool patches for DBD::Sybase and FreeTDS from Netcool Users.

Extra sidenote: If you're running Netcool in a redundant setup, define an actual database in your DBI connect statement and not the virtual database name.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.