Subject: Configuration dilemma

From: [email-masked] (Larry W. Virden)
Date: 8 Nov 1996 13:48:17 GMT

I have read the Pine readme, the FAQ, and the technical doc.  However,
I haven't been able to locate a description of where to specify during
configuration that I won't be installing things into /usr/local, so that
all the appropriate programs look in the right place for the help files, etc.
From looking at what is generated during the build execution, it appears that
via some flag notation I should be able to do this (boy, I sure wish configure
was being used - I know how to use that - and I don't even need to know 3
character machine/os names...) but I am not sure what the specific format
is.

Could someone send me an example?
-- 
:s Larry W. Virden                 INET: [email-masked]
:s <URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
:s Unless explicitly stated to the contrary, nothing in this posting should
:s be construed as representing my employer's opinions.

---

From: [email-masked] (Mike Dedek)
Date: 11 Nov 1996 19:38:49 GMT

In article <[email-masked]>, [email-masked] (Larry W. Virden) writes:
|> 
|> I have read the Pine readme, the FAQ, and the technical doc.  However,
|> I haven't been able to locate a description of where to specify during
|> configuration that I won't be installing things into /usr/local, so that
|> all the appropriate programs look in the right place for the help files, etc.
|> From looking at what is generated during the build execution, it appears that
|> via some flag notation I should be able to do this (boy, I sure wish configure
|> was being used - I know how to use that - and I don't even need to know 3
|> character machine/os names...) but I am not sure what the specific format
|> is.
|> 
|> Could someone send me an example?
|> -- 
|> :s Larry W. Virden                 INET: [email-masked]
|> :s <URL:http://www.teraform.com/%7Elvirden/> <*> O- "We are all Kosh."
|> :s Unless explicitly stated to the contrary, nothing in this posting should
|> :s be construed as representing my employer's opinions.

You need to change two variables in pine/osdep/os-xxx.h (whichever xxx 
corresponds to your system):

SYSTEM_PINERC and SYSTEM_PINERC_FIXED should be changed to the location of
the system-wide pine.conf files.

Other than that the executables are self contained and once you build them,
you should be able to move them anywhere and they'll work (providing libc.so.1
and libdl.so.1 are in the same place as where you built it).  If they are
not, changing LD_LIBRARY_PATH is probably the easiest way around it.

I hope this helps!

-Mike Dedek
 Development Services/Tools
 Lexis-Nexis, a division of Reed Elsevier PLC