Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Jack dot Marshall at barclayscapital dot com
Subject: RE: sybperl 2.11 multiple install on single host [HP-UX]
Date: Jun 9 2000 6:05PM

Finally got chance to try this out on a test system. The solution as
detailed was to
set SHLIB_PATH to the necessary oclient/lib directories.
Set "chatr +s enable +b disable" on

It seems to work fine. Many thanks.

	Jack Marshall
 	Global IT Infrastructure, Barclays Capital

-----Original Message-----
From: Andrei Nossov []
Sent: Wednesday, May 31, 2000 1:49 AM
To: SybPerl Discussion List
Subject: Re: sybperl 2.11 multiple install on single host [HP-UX]

You could try set the SHLIB_PATH environment variable
to point to the correct Open Client directory and
modify the and libraries so they
would use the SHLIB_PATH (using HP-UX utility chatr)..
It helped us when we installed a new Open Client and
didn't want to rebuild Sybperl.. You will still need
to handle the SHLIB_PATH dynamically, but it should be
a lot easier I guess..

- Andrei

--- wrote:
> > Version info first:
> > 	OS:	HP-UX 11.00 64-bit
> > 	H/w:	Any HP host
> > 	Perl	5.005_03 / 5.005_04
> > 	sybperl	2.11
> > 	oclient 	1111
> > 
> > I don't know how bizzare this question is going to
> be... a normal install
> > onto a HP-UX 11 host is fine. But we have several
> clustered (multi-node)
> > systems. Where several applications can be using
> the same perl install,
> > linked using one of the application environments.
> If the application under
> > which sybperl was compiled switches nodes for any
> reason, it takes with it
> > the sybase and the oclient installation. 
> > We can configure the interfaces file to reside
> underneath the
> > application's
> > mount-point (so it's always available). But it
> also references things like
> > oclient/lib/* - which would no longer exist and
> the shared libs all fail
> > to
> > load.
> > 
> > Has anyone found a manageable way of handling this
> without multiple
> > installations of perl on a single host. Is it
> possible to install sybperl
> > within it's own hierarchy - outside of perl5
> install dirs. We've been
> > unable
> > to compile it statically - and I assume the same
> problem would still apply
> > if we could compile it.
> > 
> > TIA...
> > 
> 	Regards,
> 	Jack Marshall
> 	Global IT Infrastructure, Barclays Capital

For more information about Barclays Capital, please
visit our web site at

Internet communications are not secure and therefore the Barclays Group
does not accept legal responsibility for the contents of this message.
Any views or opinions presented are solely those of the author and do 
not necessarily represent those of the Barclays Group unless otherwise 
specifically stated.