[GRASSLIST:4204] Re: compiling GRASS5pre5 on Cygwin gcc error

[Glynn Clements]

Thomas Dewez wrote:

> > If configure fails, you need to look at the file config.log for the
> > reason. The error messages only indicate which test failed, not why
> > the test failed.
> 
> The config.log contains the following:
> ---------snip--------------------------
> 
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> configure:680: checking host system type
> configure:703: checking for gcc
> configure:807: checking whether the C compiler (gcc  ) works
> configure:823: gcc -o conftest    conftest.c  1>&5
> configure: failed program was:
> 
> #line 818 "configure"
> #include "confdefs.h"
> 
> main(){return(0);}
> ---------snap--------------------------
> 
> Can you help me make sense of this?

Not really. Normally you would expect gcc to generate an error message
if it failed.

I can only presume that something failed at a low level, such that gcc
died suddenly.

-- 
Glynn Clements <glynn.clements at virgin.net>