[Python-Dev] Re: configure problems porting to Tru64
Martin v. Loewis
martin@v.loewis.de
18 Jul 2002 23:09:34 +0200
Jeremy Hylton <jeremy@alum.mit.edu> writes:
> (I'll also note that configure.in has a rather complex test for this,
> when it appears that autoconf has a builtin AC_FUNC_SETPGRP. Anyone
> know why we don't use this?)
That test was introduced in configure.in 1.9, on 1994/11/03. It might
well be that autoconf did not support that test at that time.
> How should we actually fix this problem? It seems to me that the
> right solution is to define _XOPEN_SOURCE in Tru64 and somehow
> guarantee that configure runs its tests with that defined, too. How
> would we achieve that?
I think it is generally the right thing to define _XOPEN_SOURCE on
Unix, providing a negative list of systems that cannot support this
setting (or preferably solving whatever problems remain).
I'd put an (unconditional) AC_DEFINE into configure.in early on; it
*should* go into confdefs.h as configure proceeds, and thus be active
when other tests are performed.
Regards,
Martin