[Bug testsuite/61606] About GCC install, testing step (mostly check...)

[fernando at info dot unlp.edu.ar]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61606

--- Comment #2 from Fernando G. Tinetti <fernando at info dot unlp.edu.ar> ---
(In reply to kargl from comment #1)
> (In reply to Fernando G. Tinetti from comment #0)
> > Hi,
> > 
> > I'm making my own todo list for GCC install from sources, given that at some
> > point I would like to contribute to gfortran, if possible (I'm rather far
> > from it right now). Just to be clear, my todo list to install from sources
> > is at
> > http://fernando.usr.me/GCC-gfortran-install.html
> > (maybe it would be useful some day for enhancing the online documentation...
> > maybe not...).
> > 
> 
> Please the installation instructions at https://gcc.gnu.org/install/
> Your custom installation method as outlines in your blog above is
> clearly broken.
> 
> -- 
> steve

Hi steve, thanks for asking.

I cannot see how "is clearly broken", I think I've followed the installation
steps you point out (also referred to in my "custom method").

Would you please tell me what I did miss/misunderstand/broke? I'm also confused
since following the steps in my custom method actually works at least
sometimes, and the initial difference is "only" about the reported timeout in
the failing cases. Also, please take a look at my questions about

>>> Is there a single way to look for PASS/FAIL answer to the GCC check 
>>> step? I mean: nothing went out of normal would mean PASS, otherwise 
>>> FAIL.
>>>
>>> Are the *.sum and *.log in the directories shown/used by 
>>> ../gcc-4.9.0/contrib/test_summary?

since I cannot find the answers to these questions in the URL you 
provided.

TIA,

Fernando.