Michael Hudson
2002-07-17 09:06:07 UTC
Actually, could you look at line 866 of posixmodule.c, where is says
#ifdef __hpux
extern int fdatasync(int); /* On HP-UX, in libc but not in unistd.h */
#endif
and change this to
#if defined(__hpux) || defined(_AIX)
extern int fdatasync(int); /* On HP-UX and AIX, in libc but not in
unistd.h */
#endif
and see if that helps? Do AIX and HP-UX share some common ancestry?
They seem to require a lot of similar portability hacks.
If this works, I'll check it in for rc2.
Has this disappeared from CVS or was it never checked in?#ifdef __hpux
extern int fdatasync(int); /* On HP-UX, in libc but not in unistd.h */
#endif
and change this to
#if defined(__hpux) || defined(_AIX)
extern int fdatasync(int); /* On HP-UX and AIX, in libc but not in
unistd.h */
#endif
and see if that helps? Do AIX and HP-UX share some common ancestry?
They seem to require a lot of similar portability hacks.
If this works, I'll check it in for rc2.
Given that 2.3 uses autoconf 2.5.something it would be better to use
the AC_CHECK_DECLS (or whatever it's called) macro to tell whether we
need to declare it ourselves. I haven't found the time to acquire the
necessary autoconf-fu to do this yet.
Backporting the autoconf 2.5 work to 2.2 is something else I've been
meaning to look at (at least partially for this reason).
Cheers,
M.
--
40. There are two ways to write error-free programs; only the third
one works.
-- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html
40. There are two ways to write error-free programs; only the third
one works.
-- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html