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 Jeffrey.Armstrong
Recipients Jeffrey.Armstrong
Date 2014-10-08.13:26:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1412774815.08.0.905106017715.issue22579@psf.upfronthosting.co.za>
In-reply-to
Content
The determination of the name of the posix module's initialization function (at Modules/posixmodule.c:12055)  is currently dependent on the compiler being used.  For MSVC, Watcom, or Borland, the name is defined as "PyInit_nt."  However, both Open Watcom and Borland have shipped compilers for GNU/Linux (and other platforms), making determining the posix module initialization function based on compiler incorrect.

Most other places in Modules/posixmodule.c correctly use the "MS_WINDOWS" preprocessor definition to determine if Windows routines should be used.  Naming the intialization function for the posix module should be dependent on this as well rather than compiler identifiers.  

Linking the interpreter natively with Open Watcom fails under GNU/Linux due to "PyInit_posix" being undefined.  This occurs because of the reasons described above.  The patch included corrects the issue.
History
Date User Action Args
2014-10-08 13:26:55Jeffrey.Armstrongsetrecipients: + Jeffrey.Armstrong
2014-10-08 13:26:55Jeffrey.Armstrongsetmessageid: <1412774815.08.0.905106017715.issue22579@psf.upfronthosting.co.za>
2014-10-08 13:26:55Jeffrey.Armstronglinkissue22579 messages
2014-10-08 13:26:54Jeffrey.Armstrongcreate