Re: Linux Intel Requirements to Build egcs

[Jim Wilson <wilson at cygnus dot com>]

	I'm new to the list and I haven't been able to build any of the ecgs
	binaries from 971031.  I always end up with cpp usage errors in various
	places.

This usually indicates that some environment variable is set incorrectly.
If one of the environment variables that gcc uses has an explicit or implicit
`.' among the list of filenames, then the old gcc that you are using to
compile EGCS will accidentally try to load and use some of the new files in
EGCS, and the old gcc gets confused because of incompatibilities because
the old and new versions of these files.

If you fix your environment variable, then the problem will go away.  The
most likely culprits are COMPILER_PATH, LIBRARY_PATH, and LPATH.  If any
of these have an explicit `.' in them, or if they start or end with a
colon (which adds an implicit `.' to the directory list) then this is what
is causing EGCS to fail.

	Do I need libgcc2?

All targets need libgcc2.  libgcc2 is part of gcc, and will automatically
be built.  There is no need to worry about.

	Also what ./configure options should I be using for this settup?

I don't know.

	(I noticed that autoconf always generates gcc/Makefile with
	USE_COLLECT=ld even if I don't specify --with-gnu-ld.  Is this an error?
	I remove this by hand my compile goes much further but still fails.)

No, this isn't an error.  This tells gcc to build collect2.  Collect2 is
always needed now, regardless of whether GNU ld is being used, because collect2
includes C++ template instantiation support which is not in GNU ld.

Jim