Re: V3 still misdetecting GCC 3.0? [on Alaph Tru64 5.0 system]

[Mumit Khan <khan at NanoTech dot Wisc dot EDU>]

On Mon, 2 Jul 2001, Benjamin Kosnik wrote:

> 
> > I thought we had fixed this.
> 
> Me too.
> 
> > Does anyone know what the problem is?
> 
> No. Can you send me the config.log bit that's relevant?
> 
> I'm not quite sure we even need to do this anymore. It seems to be 
> causing more grief than it's worth.

Perhaps we have different problems, but mine is rather obvious when
you look at the libstdc++-v3/config.log file -- cc1plus dies with
an internal error on any input, causing configure to guess incorrectly.

Here's a snippet:

  <internal>:0: Internal error #536854048.
  <internal>:0: Internal compiler error in , at ^A:536854032
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
  ltconfig: failed program was:
  #ifdef __cplusplus
  extern "C" {
  #endif
  char nm_test_var;
  void nm_test_func(){}
  #ifdef __cplusplus
  }
  #endif
  int main(){nm_test_var='a';nm_test_func();return(0);}

  $ ./xgcc -B./ -v
  fada.nanotech.wisc.edu> ./xgcc -B./ -v
  Reading specs from ./specs
  Configured with: ../../gcc-3.0/configure --enable-shared
  --enable-languages=c++,f77 --prefix=/usr/local/gcc-3.0
  Thread model: single
  gcc version 3.0

  $ ../../../gcc-3.0/config.guess
  alpha-dec-osf5.0

  (It's a 5.0A machine, patched with a recent patchset from Compaq)


I guess it's time to build a debugging version. If only building GCC
didn't take so long on this pathetic little machine.

Regards,
Mumit