On Tue, Oct 16, 2001 at 08:06:53AM -0400, [EMAIL PROTECTED] wrote:
>
> On Tue, 16 Oct 2001, Raja R Harinath wrote:
>
> > [EMAIL PROTECTED] writes:
> > > On Mon, 15 Oct 2001, Gary V. Vaughan wrote:
> > >> On Sun, Oct 14, 2001 at 10:03:38PM -0400, [EMAIL PROTECTED] wrote:
> > >> > Is there a way t
On Tue, 16 Oct 2001, Raja R Harinath wrote:
> [EMAIL PROTECTED] writes:
> > On Mon, 15 Oct 2001, Gary V. Vaughan wrote:
> >> On Sun, Oct 14, 2001 at 10:03:38PM -0400, [EMAIL PROTECTED] wrote:
> >> > Is there a way to tell libtool that it needs to set some additional
> >> > runtime variables i
[EMAIL PROTECTED] writes:
> On Mon, 15 Oct 2001, Gary V. Vaughan wrote:
>> On Sun, Oct 14, 2001 at 10:03:38PM -0400, [EMAIL PROTECTED] wrote:
>> > Is there a way to tell libtool that it needs to set some additional
>> > runtime variables in addition to LD_LIBRARY_PATH when trying to test run
>> >
On Mon, 15 Oct 2001, Gary V. Vaughan wrote:
> On Sun, Oct 14, 2001 at 10:03:38PM -0400, [EMAIL PROTECTED] wrote:
> >
> > Is there a way to tell libtool that it needs to set some additional
> > runtime variables in addition to LD_LIBRARY_PATH when trying to test run
> > an executible before i
On Sun, Oct 14, 2001 at 10:03:38PM -0400, [EMAIL PROTECTED] wrote:
>
> Is there a way to tell libtool that it needs to set some additional
> runtime variables in addition to LD_LIBRARY_PATH when trying to test run
> an executible before its installed? I have some data files and the path
> gets b
Is there a way to tell libtool that it needs to set some additional
runtime variables in addition to LD_LIBRARY_PATH when trying to test run
an executible before its installed? I have some data files and the path
gets built into the binary, but can be overridden with an environment
variable.
I
