Up Prev Next
From: Michael Peppler <mpeppler at peppler dot org>
Subject: Re: Sybase home directory question
Date: Nov 23 2004 7:21AM
On Mon, 2004-11-22 at 19:47, Christian Behrens wrote:
> > > That is very strange. CTlib.pm and DBlib.pm both had ../sybase/OCS-12_5
> > in
> > > them. Why? My CONFIG file clearly has not OCS-12_5 in it. And no
> > variable is
> > > set, and I don't think I had anything set when building SybPerl.
> > Although
> > > that is easy enough to test which I'll probably do later.
> > That's a bug. I looked through the code, and I see that I override the
> > value of SYBASE and append the OCS bit to it if it is found/set in the
> > environment.
> OK, you're right, I must have had $SYBASE_OCS set to successfully run 'make
> test', that just occurred to me. However, is this bug on Solaris only?
No - it's a generic bug.
> > > The other weird thing is that after fixing CTlib.pm and DBlib.pm, my
> > test
> > > script DOES work and gives me back the the version string of the server
> > I'm
> > > connecting to, but without having anything else (i.e. $SYBASE_OCS) set.
> > Now
> > > this is great and exactly what I wanted, however not what I expected,
> > after
> > > this didn't work on Linux (had to add ../sybase/OCS to ld.so.conf).
> > On Solaris this is normal - the path to the libraries is written to the
> > binary because either the LD_RUN_PATH env. variable is set at compile
> > time or because the -R link option is used (I don't have a Solaris box
> > to test with right now, but I'm pretty sure that that's what is going
> > on.)
> That's also on Solaris only, right?
And any other platform that supports the LD_RUN_PATH/-R option.
Michael Peppler Data Migrations, Inc.
Sybase T-SQL/OpenClient/OpenServer/C/Perl developer available for short or
long term contract positions - http://www.peppler.org/resume.html