Re: could not setup config headers machinery

[Dr. David Kirkby]

On 10/25/10 07:15 PM, Eric Blake wrote:
> On 10/23/2010 10:25 AM, Dr. David Kirkby wrote:
> > On 10/14/10 09:02 PM, Ralf Wildenhues wrote:
>
> > > > checking for IEEE denormalized values... yes
> > > > configure: creating ./config.status
> > > > config.status: error: invalid argument: `Makefile.'
>
> > > Can you send 'diff -u' of the two configure files (without above line
> > > and with)? Of even of the one with float.h and the one with math.h?
> >
> >
> > Sure. First here's the diff between the configure.ac files
>
> Thanks.
>
> > What is also interesting is the difference between that which looks in
> > the math.h file and that which looks in the float.h file:
> >
> > i.e.
> >
> > address@hidden:~/gsl-1.14$ diff -u configure.ac.math configure.ac.float
> > --- configure.ac.math Sat Oct 23 16:55:44 2010
> > +++ configure.ac.float Sat Oct 23 16:54:20 2010
> > @@ -197,7 +197,7 @@
> > AC_CHECK_DECLS(atanh,,,[#include <math.h>])
> > AC_CHECK_DECLS(ldexp,,,[#include <math.h>])
> > AC_CHECK_DECLS(frexp,,,[#include <math.h>])
> > -AC_CHECK_DECLS([fprnd_t],[],[],[[#include <math.h>]])
> > +AC_CHECK_DECLS([fprnd_t],[],[],[[#include <float.h>]])
>
> I'm wondering if we are tripping on some sort of length-based bug (that
> is, in the past, we have evidence where some shells mishandle here-docs
> that contain a ${...} expansion across a page boundary; maybe this is a
> similar case). If it is indeed a length-based bug, does adding one more
> byte in the <math.h> approach also make the bug appear?



I've played around with this a bit. What I found was

1) changing float.h to a header file with a smaller name, or a longer one made 
no difference.

2) Building the configure script on a Linux system, with autoconf 2.14 rather 
than the OpenSolaris system with 2.65 made the problem go away.

3) Changing the versions of sed and awk on the OpenSolaris machine to be the GNU 
versions, made no difference

4) Finally upgrading autoconf from 2.65 to the latest (2.68) on the Sun made the 
problem go away. So I wonder if its a bug in autoconf 2.65, which does not exist 
on either 2.10 or 2.68.

So the problem is solved by updating to the latest autoconf


Dave

Dave