[issue9060] Python/dup2.c doesn't compile on (at least) newlib

Amaury Forgeot d'Arc added the comment: > but Python 2.x doesn't appear to actually bother > to compile dup2.c even if the system lacks dup2 Is it sure? The file configure.in has the same command in both versions: AC_REPLACE_FUNCS(dup2 getcwd strdup) Added the #include anyway in r85236, r

[issue9060] Python/dup2.c doesn't compile on (at least) newlib

Antoine Pitrou added the comment: (as a sidenote, the last significant changes to dup2.c date back from 1994) -- nosy: +gvanrossum, loewis, pitrou versions: +Python 3.2 ___ Python tracker __

[issue9060] Python/dup2.c doesn't compile on (at least) newlib

New submission from Torne Wuff : On systems without dup2(), Python tries to compile its own from Python/dup2.c, but this file refers to close() without including unistd.h. This causes it to not compile with newlib (and possibly other C libraries, presumably it was relying on fcntl.h indirectly