This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kramm
Recipients
Date 2005-03-07.10:29:04
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=1146139

That's a problem which isn't introduced by this patch.
In posixmodule.c, a lot of code fragments already read like

#if _THISORTHATCOMPILER_
#define HAVE_FUNCTION_FOO
#define HAVE_FUNCTION_BAR
#endif

That is, autoconf only determines the used compiler, and
posixmodule.c uses that to make assumptions about which
functions are present.
That's also exactly what breaks MingW compilation- as
posixmodule.c doesn't know anything about MingW as compiler,
it defaults on gcc, and hence derives the wrong set of
available functions.

This patches fixes that in making posixmodule.c "MingW-aware".

I don't know why posixmodule.c was implemented in that way,
instead of making autoconf determine all those HAVE_ flags-
maybe that's a question which should go to
python-dev@python.org. But for now, as that's what the
current implementation does, this patch is consistent with
that approach.

Greetings

Matthias
History
Date User Action Args
2007-08-23 15:40:21adminlinkissue1053879 messages
2007-08-23 15:40:21admincreate