On 07 Aug 2002 01:26:21 +0200, Dominik Vogt wrote: > > Apart from that, your problem is simply a bug in the configure.in > script. I forgot to call AC_CHECK_HEADERS(sys/time.h), so > sys/time.h gets never included on some systems.
I think this is not the case here. HAVE_SYS_TIME_H was defined even without an explicit check for sys/time.h. > On Tue, Aug 06, 2002 at 10:01:56PM +0000, Mikhael Goikhman wrote: > > > > With my glibc-2.2.5, time.h and > > sys/time.h are two different things although sys/time.h includes some > > portion of time.h, but not all. > > > > So after this commit modules/FvwmTaskBar/Goodies,c fails to compile and > > > modules/FvwmWharf/FvwmWharf.c produces a warning (implicit declaration of > > function `time'). Adding #include <time.h> in both solves the problem. > > Hm, that's funny. I'd have expected that with the bug in > configure.in only time.h would have been included, not sys/time.h. > Is it possible that the order in which the files are included is > important? And which autoconf version do you have? What messages > about the time headers do you get in configure? I am trying to move fvwm to autoconf-2.53, still not fully successful, so autoheader (and some other things) do not work for me. I downgraded to autoconf-2.13 (the only relable autoconf version for now) and this time.h problems disappeared. I know why it is. TIME_WITH_SYS_TIME is now defined, but it was not defined before you uncommented AC_HEADER_TIME and my config.h can't be regenerated with autoconf-2.53. At least I learned where this TIME_WITH_SYS_TIME gets defined. I returned to autoconf-2.53 and will try to defeat it soon. Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
