PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: John_McCarthy at WellspringRes dot com
Subject: RE: Invocation Problem
Date: Mar 20 2000 9:59PM

I have discovered that when we built sybperl, that DBlib.pm and DBlib.sl
both ended up with "hardcoded" references to:
$SYBASE/lib/libsybdb.sl and $SYBASE/lib/lininsck.sl using the value of
$SYBASE at the time of the build.  Subsequently changing the values of
$SYBASE to point to a different valid directory will cause the job to fail
if the original directory no longer exists.

Is this the way it is supposed to work?  Can you only use sybperl with one
release?  Do you have to rebuild sybperl everytime you change your $SYBASE
release directory?  Is there any way to make DBLib.{pm|sl} look at the
current value of $SYBASE?

> Subject:	Invocation Problem
> 
> At line 34, my perl script contains:
> use Sybase::Sybperl;
> 
> When run, this script produces these messages:
> Can't load
> '/usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/auto/Sybase/DBlib/DB
> li
> b.sl' for module Sybase::DBlib: No such file or directory at
> /usr/local/apps/perl5/lib/5.00503/PA-RISC2.0/DynaLoader.pm line 169.
> 
>  at /usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/Sybase/Sybperl.pm
> line 79
> BEGIN failed--compilation aborted at
> /usr/local/apps/perl5/lib/site_perl/5.005/PA-RISC2.0/Sybase/Sybperl.pm
> line
> 79.
> BEGIN failed--compilation aborted at
> /usr/local/dbsystems/sybadm/bin/server.stats line 34.
>