| On Fri, Jan 19, 2001 at 03:11:13PM +0100, Akim Demaille wrote:
| > Patrick, could you try again?  There were problem with AC_LANG which
| > might be responsible.  Compared to the two days old Autoconf, the only
| > significant difference I see is:
| 
| Yes, you got it!
| 
| All 175 tests were successful (36 skipped)

you don't have GNU sed, right?

| > So I do expect your Fortran 77 compiler to be diagnosed again as
| > broken.
| 
| Indeed:
| 
| 71. ./syntax.at:27: testing AC_F77_WRAPPERS...
| ./syntax.at:27: autoconf --autoconf-dir .. -l $at_srcdir
| ./syntax.at:27: autoheader --autoconf-dir .. -l $at_srcdir
| ./syntax.at:27: top_srcdir=$top_srcdir ./configure
| --- empty       Fri Jan 19 15:02:05 2001
| +++ stderr      Fri Jan 19 15:02:09 2001
| @@ -0,0 +1 @@
| +configure: error: Fortran 77 compiler cannot create executables
| checking for g77... g77
| checking whether the Fortran 77 compiler works... no
| 71. ./syntax.at:27: ok (skipped near `syntax.at:27')
| 
| 
| (Using GNU Fortran 0.5.24-19981002)
| quartz% cat this.f
|       program this
|       write(*,*)'Hello World'
|       end
| quartz% f77 this.f
| /usr/lib/libg2c.so: warning: tempnam() possibly used unsafely, use mkstemp() or 
|mkdtemp()
| quartz% a.out
|  Hello World
| 
| But that is no longer an autoconf's problem..

Personally I'd say something's still fishy.  Why do you agree with
configure when it says your compiler is broken?  If you study
config.log after having run

./testsuite -d -v 27

do you agree with its decision?  If it doesn't make sense to you,
please send us config.log.

Reply via email to