Dear monks,

can you think of a reason why setting $ENV{foo} wouldn't be exported to a child process? Funny, I have two versions of perl-5.8.5, compiled with different threading options, which show different results: 

/path1/perl (5.008005): Export OK
/path2/perl (5.008005): Export not OK

[download]
on 
$ENV{foo} = "abc";
my $out = `echo \$foo`;

print "$^X ($]): Export ",
      $out ne "abc\n" ? "not " : "",
      "OK\n";

[download]
The difference between the two binaries is that one got linked to linuxthreads, while the other one uses pthreads, both on FreeBSD 4.x.

Weird, isn't it? Doesn't setting %ENV just translate to a setenv() at C-level?

In reply to %ENV setting not exported to child process? by saintmike

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.