tech-toolchain archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: debugging early failure of (in rebuilding nbmake)

On Sun, 13 Jan 2013, matthew green wrote:
        ===> Bootstrapping nbmake
        checking for sh... /bin/sh
        checking for gcc... cc
        checking for C compiler default output... configure: error: C compiler  
cannot create executables
        ERROR: Configure of nbmake failed
        *** BUILD ABORTED ***

config.log can be pretty large, and the useful parts are usually at around the 60% mark of the file. dumping the whole thing the users terminal seems overly excessive to me, but perhaps printing the path to the file with a suggestion on what to look for would be good enough.

Yes, dumping the whole thing to stdout or stderr seems excessive. However, the work is done in a temporary directory, which is removed on exit, so just printing the path to the file probably won't work; we'd also have to copy the log file somewhere more permanent, or somehow disable the removal of ${tmpdir} in this case.

--apb (Alan Barrett)

Home | Main Index | Thread Index | Old Index