removing aclocal.m4
Can we remove aclocal.m4? The last log message states: fix for bug #811160 - autoconf vs. hp/ux system header files. also applied to release23-maint. Note that aclocal.m4 can go away when autoconf 2.58 is out. And configure says: # Generated by GNU Autoconf 2.59 for python 2.5. Neal
Neal Norwitz wrote:
Can we remove aclocal.m4? The last log message states:
fix for bug #811160 - autoconf vs. hp/ux system header files. also applied to release23-maint.
Note that aclocal.m4 can go away when autoconf 2.58 is out.
It appears to me that 2.59 indeed fixes the HP-UX problem; a diff with and without aclocal.m4 shows chunks like cat confdefs.h >>conftest.$ac_ext cat >>conftest.$ac_ext <<_ACEOF /* end confdefs.h. */ +/* Define $ac_func to an innocuous variant, in case <limits.h> declares $ac_func. + For example, HP-UX 11i <limits.h> declares gettimeofday. */ +#define $ac_func innocuous_$ac_func + /* System header to define __stub macros and hopefully few prototypes, which can conflict with char $ac_func (); below. Prefer <limits.h> to <assert.h> if __STDC__ is defined, since - <limits.h> exists even on freestanding compilers. Under hpux, - including <limits.h> includes <sys/time.h> and causes problems - checking for functions defined therein. */ -#if defined (__STDC__) && !defined (_HPUX_SOURCE) + <limits.h> exists even on freestanding compilers. */ + +#ifdef __STDC__ # include <limits.h> #else # include <assert.h> #endif + +#undef $ac_func + So they manage to get limits.h define, say, innoucuous_clock(), instead of clock(), whereas we currently avoid including limits.h on HP-UX. IOW, it seems like it should work, but somebody should test it on HP-UX to be sure. Regards, Martin
participants (2)
-
"Martin v. Löwis" -
Neal Norwitz