The problem is even if you do it that way the linker already
has LD_LIBRARY_PATH cached and you can't change it.
The linker is started (and caches LD_LIBRARY_PATH) as
soon as perl is started. You really need to set LD_LIBRARY_PATH
before perl even starts.
Other that just setting LD_LIBRARY_PATH in the environment
the only solution
I came up with
was to set the environment, fork, and
have the new process do the
DB work. But that was kind of hokey and I didn't like
spawning the second process to do the work. I tried to look
for ways of chainging solaris's linker to not cache
LD_LIBRARY_PATH but never got very far.
BTW, LD_LIBRARY_PATH (and any other environmental vars used
by the linker) are the only ones you need to worry about.
You're OK setting other environmental vars
(ORACLE_HOME, TNS_ADMIN, etc...) in your
perl script. The problem is strictly related to the
behavior of solaris's linker.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.