On Wed, Mar 02, 2011 at 07:16:19AM +0100, Ralf Wildenhues wrote:
> Hello Dave,
> 
> * Dave Korn wrote on Wed, Mar 02, 2011 at 06:28:15AM CET:
> >      http://mad-scientist.net/make/autodep.html
> > 
> > although note that where that recommends using "-include" (under
> > "Avoiding ``No rule to make target ...'' Errors") to ignore would-be
> > errors from trying to include non-existent files, we use an unprefixed
> > include directive to read them in our Makefiles, and rely on
> > config.status to generate empty ones first time round.  I'm not sure
> > why we do that differently.
> 
> That's because non-GNU makes don't have facilities to include a file
> only if it is present, and with the current machinery, a non-present
> file always indicates a bug (or previous error) and having errors be
> loud is a good thing for debugging.
> 
> Jack, the actual issue you're seeing might well be the result of some
> missing dependency.  With parallel build failures, it is most important
> to see output from make, back to at least the first error that happened.
> That can be arbitrarily far back, and in GCC it is not uncommon to have
> it happen a few thousand lines before the end of the log.  Please save
> such logs for future reports.
> 
> Thanks,
> Ralf

Ralf,
    A second repetition of the original build with --enable-build-with-cxx
completed without errors. FYI, I do all of my builds on darwin10 with
lto-bootstrap and 'make -j 8'. This is the first time that I have seen this
particular failure crop up.
         Jack

Reply via email to