http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48621
--- Comment #4 from Georg Bauhaus <bauhaus at futureapps dot de> 2011-04-15 16:55:15 UTC --- (In reply to comment #3) > > I have started again using a absolute path to configure, as you have > > suggested. > > Thanks, let's see whether this changes something. Findings so far: I omitted $ make check this time and everything, including the gcc driver program, was properly installed into /usr/local/bin . GNAT Lib v4.4 is still on line 1 of gcc/ada/doctools/xgnatugn.ali but there is no sign of a problem with it. A possible cause for the issue might have been here: I have run $ make check now, and apparently it hit a memory limit and tore the machine down (up to "no processes to kill"). Since I had run $ make check before I had tried # make install during the previous attempt, the missing "gcc" executable might simply have been a lost when at some point the file system needed fixing. Or some other unknown. My bad. Setting ulimits for $ make check accordingly looks promising. If everything runs well, I will be happy, and silent.
