Instead of reimplementing one of the commands in Perl, you can be the shell! 
use strict;
use warnings;

use IPC::Open3 qw( open3 );

my $make_file = 'Makefile';

open(local *TO_MAKE, '<&', *STDIN) or die;
*TO_MAKE if 0;  # Avoid spurious warning.
my $make_pid = open3(
   '<&TO_MAKE',
   local *FR_MAKE,
   undef,
   'make', '-f', $make_file,
);

*FR_MAKE if 0;  # Avoid spurious warning.
my $tee_pid = open3(
   '<&FR_MAKE',
   '>&STDOUT',
   undef,
   'tee', '-a', 'build.log',
);

waitpid($make_pid, 0);
print("$?\n");

waitpid($tee_pid, 0);
print("$?\n");

[download]

Duplicating our STDIN instead of using '<&STDIN' is necessary since open3 closes the handle we pass for the child's STDIN.

In reply to Re: Capture Exit Code Using Pipe & Tee by ikegami
in thread Capture Exit Code Using Pipe & Tee by Anonymous Monk

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.