A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-July/026727.html below:

configure problems porting to Tru64

[Python-Dev] Re: configure problems porting to Tru64 [Python-Dev] Re: configure problems porting to Tru64Martin 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




RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4