Chapter 6: gcc needs autoconf to compile

[John_Linux@…]

I have come accross this same problem mentioned in Bug 186 in version 3.3. My install was from a RedHat 7.3 system.

Basically Autoconf and Lex are required which in turn require M4, and perl. Lex requires yacc and bison.

[markh@…]

gcc only needs autoconf to compile if certain file timestamps have been messed up (usually those involving configure.{in,ac} and the other autoconf files) as I said in this mail to Timothy just now:

Doesn't look credible to me. It looks like the configure.{ac,in} or similar file has been touched which is forcing gcc to regenerate the configure file. If the poster tries reuntarring gcc and rebuilding it, it should be fine. It could also *concievably* occur if they're reusing the gcc source tree from chapter05 though I doubt it. Finally, it could be due to clock skew.

What I'm 99% sure of, is that it isn't related to RH-7.3 ;-)

The best course of action for the reporter is to delete the gcc source tree and gcc-build and re-untar the package, then try configuring again. If this still doesn't work, I'd suspect either a corrupt tarball (you didn't patch up to gcc-3.1 did you, you should get a new tarball; the GNU patches have a tendency to cause problems) or some sort of nasty clock skew.

Resolving as invalid. If the reporter has further problems, email the lfs-support list where we will be happy to help them.