Others have suggested File::Find, but File::Find::Rule makes tasks like this easier. Try something like this (untested code): 
use File::Find::Rule;

my @file = find( file =>
    name => '*.cc',
    in => '/clearb/pa/wBcn' ) or die "Find Failed: $!";

foreach (@file) {
    s/\.cc$/.cpp/;
    @args = system('/usr/bin/make', '-f', $_);
    $args == 0 or die "system @args failed: $?";
}

[download]
I also use perlfunc:system instead of backticks because you're not capturing the output of the make command. Also, this may be more secure because system with multiple arguments does not parse shell metacharacters such as * and ..

In reply to Re: greping in subdir by tomhukins
in thread greping in subdir by DS

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.