> > Are you calling it with gcc? I think with egcs you have to use g++ as
> > the calling program, not gcc.
> Yes, I usually do so. In my previous Linux installation (Redhat 4.2) it
> worked just fine.
> Is there a point in removing that feature from gcc?
I believe if you read the friendly RedHat documentation, it says right up in
the front, that /usr/bin/gcc will call the older 184.108.40.206 compiler, and that if
you use /usr/bin/egcs compiler it will use the egcs-2.90.27 980315 (egcs-1.0.2
release) version, and that if you want to compile C++ or Fortran code, you must
use an egcs compiler (ie, either use the g++ version of the driver, or use
The reason why /usr/bin/gcc is not egcs based, is because the 2.0.xx kernels
will not build with egcs (the failure I'm most familar with is ioport.c which
has invalid asm constraints that 2.7.xx generated mostly correct code, but the
egcs compilers don't). The maintainers of 2.0.xx kernels have stated that they
won't be fixing this in the near term. The 2.1.xx development kernels build
quite well with egcs (and the fsf 2.8.1 compiler, but that is buggier than
Michael Meissner, Cygnus Solutions (Massachusetts office)
4th floor, 955 Massachusetts Avenue, Cambridge, MA 02139, USA