mktime not working?

[Stefan Monnier]

when I do "./configure --with-ns" on my Debian testing machine, it hangs
on "checking for working mktime..." for a minute, and finally concludes
that mktime is not working.

Does anybody know what's up with that?


        Stefan

[Glenn Morris-3]

Stefan Monnier wrote:

> when I do "./configure --with-ns" on my Debian testing machine, it hangs
> on "checking for working mktime..." for a minute, and finally concludes
> that mktime is not working.

It's some AC_FUNC_MKTIME/gcc thing. Eg:

http://lists.debian.org/debian-gcc/2008/03/msg00261.html

I noticed Andreas applied some manual configure tweak in rev 1.277.

[Glenn Morris-3]

PS Probably running Debian testing's (patched?) autoconf will fix it.

[Angelo Graziosi-2]

Stefan Monnier wrote:
 > when I do "./configure --with-ns" on my Debian testing machine, it
 > hangs on "checking for working mktime..." for a minute, and finally
 > concludes that mktime is not working.

Just for completeness... the same behaviour happens on Cygwin, using
gcc-4.3.1 and ./configure.


Cheers,
    Angelo.

[Kent Engstrom]

Angelo Graziosi <angelo.graziosi@...> writes:
> Stefan Monnier wrote:
>> when I do "./configure --with-ns" on my Debian testing machine, it
>> hangs on "checking for working mktime..." for a minute, and finally
>> concludes that mktime is not working.
>
> Just for completeness... the same behaviour happens on Cygwin, using
> gcc-4.3.1 and ./configure.

Same on Fedora 9 too.

/ Kent Engström, Lysator

[Sven Joachim]

On 2008-07-28 22:37 +0200, Kent Engstrom wrote:

> Angelo Graziosi <angelo.graziosi@...> writes:
>> Stefan Monnier wrote:
>>> when I do "./configure --with-ns" on my Debian testing machine, it
>>> hangs on "checking for working mktime..." for a minute, and finally
>>> concludes that mktime is not working.
>>
>> Just for completeness... the same behaviour happens on Cygwin, using
>> gcc-4.3.1 and ./configure.
>
> Same on Fedora 9 too.

It happens on all platforms with GCC 4.3.  The solution is to regenerate
`configure' with a recent version of autoconf (2.62, or Debian's 2.61-7).
See http://permalink.gmane.org/gmane.linux.debian.devel.general/126299.

Sven

[Glenn Morris-3]

Sven Joachim wrote:

> It happens on all platforms with GCC 4.3.  The solution is to regenerate
> `configure' with a recent version of autoconf (2.62, or Debian's 2.61-7).

This will keep coming back (as it just has done) unless we require all
developers to use Debian, which is impossible, or change to
AC_PREREQ(2.62).