https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668
--- Comment #4 from Pei JIA ---
I just strictly follow
http://linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html,
and I'm using the following command line:
su nobody -s /bin/bash -c "PATH=$PATH make -k check"
Should I do:
su nobody -s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668
--- Comment #3 from Andrew Pinski ---
You can also look at the progress by tail -f gcc.log or gcc.sum if you want.
But yes there are many testcases which causes this to be slow especially if you
are not using -j.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668
--- Comment #1 from Jonathan Wakely ---
(In reply to Pei JIA from comment #0)
> So, my questions are:
>
> Is make[2]: autogen: Command not found an ERROR? Is autogen required?
This seems pretty clearly documented at
https://gcc.gnu.org/inst
