From perldoc IPC::Open3:
It will not create these file handles for you. You have to do this yourself. So don't pass it empty variables expecting them to get filled in for you.
So you can't pass FAKEHANDLE like you do; instead, you'd need to open /dev/null for reading and pass that.

However, if as in your example you're not interested in communicating with your process as it runs, why not just say 

system("$make_cmd -v -f $makefile > $outlog_filename 2> $errlog_filena
+me")

[download]
instead?

In reply to Re: Re: Segmentation Fault - Child/Output collision? by ariels
in thread Segmentation Fault - Child/Output collision? by Stormr

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.