Here's a "something close" for cases where you need multiple elements in your path.

BEGIN { my $dir; my $needed_path = 0; my @need = ( "/usr/local/lib", "/usr/platform/SUNW,Ultra-80/lib", "/usr/lib" ); my $ld_path = $ENV{LD_LIBRARY_PATH}; if( ! $ld_path ) { $ENV{LD_LIBRARY_PATH} = join ":", @need; exec 'env', $^X, $0, @ARGV; } foreach $dir (@need) { if ( $ld_path !~ m/(^|:)\Q$dir\E(:|$)/ ) { $ENV{LD_LIBRARY_PATH} .= ':' . $dir; $needed_path = 1; } } if($needed_path) { exec 'env', $^X, $0, @ARGV; } }
Be Appropriate && Follow Your Curiosity

In reply to Re^2: programatically setting the LD_LIBRARY_PATH by mikeraz
in thread programatically setting the LD_LIBRARY_PATH by LanceDeeply

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.