[Bug c++/89668] make[2]: autogen: Command not found

2019-03-12 Thread egallager at gcc dot gnu.org 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668

Eric Gallager  changed:

   What|Removed |Added

 CC||egallager at gcc dot gnu.org

--- Comment #5 from Eric Gallager  ---
(In reply to Pei JIA from comment #4)
> 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 /bin/bash -c "PATH=$PATH make -k -j8 check" instead??

I'd also add RUNTESTFLAGS=-v

[Bug c++/89668] make[2]: autogen: Command not found

2019-03-11 Thread jiapei at longervision dot com 
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 /bin/bash -c "PATH=$PATH make -k -j8 check" instead??

[Bug c++/89668] make[2]: autogen: Command not found

2019-03-11 Thread pinskia at gcc dot gnu.org 
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.

[Bug c++/89668] make[2]: autogen: Command not found

2019-03-11 Thread redi at gcc dot gnu.org 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89668

Jonathan Wakely  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

--- Comment #2 from Jonathan Wakely  ---
This doesn't seem like a bug.

If you have questions, please use the gcc-help mailing list, not a bug report.

[Bug c++/89668] make[2]: autogen: Command not found

2019-03-11 Thread redi at gcc dot gnu.org 
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/install/prerequisites.html

> Is WARNING: Couldn't find the global config file. an ERROR? It looks
> like it's just a harmless warning, right?

You can ignore it.

> Any suggestions? Should I just wait? But, it's already been hours

There are thousands and thousands of tests. You probably should have told make
to run multiple jobs at once, using the -j option and an argument.