[issue9098] MSYS build fails with `S_IXGRP' undeclared

STINNER Victor added the comment: No activity since 2012, I close the issue. -- nosy: +vstinner resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker __

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Changes by Roumen Petrov : -- nosy: +rpetrov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue9098] MSYS build fails with `S_IXGRP' undeclared

mewalig added the comment: If I am reading this right, then in the below part of the patch, slave_name does not get set before it is used if __MINGW32__ is not defined. this can be fixed by moving the "#endif" up to the line before slave_name = ptsname(master_fd); /* get name of slave */

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Olivier Refalo added the comment: hum, your patch actually works on MSYS ! ok.. so I am pretty much having the very some issue. Could not find platform dependent libraries Consider setting $PYTHONHOME to [:] Fatal Python error: Py_Initialize: unable to load the file system codec LookupError:

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Yuri added the comment: I fixed all build problems on the current MinGW32. python.exe builds ok, but build fails since python.exe can't find some modules after this. Not sure why. -- keywords: +patch nosy: +yurivict Added file: http://bugs.python.org/file22329/python-3.2.patch ___

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Martin v. Löwis added the comment: Martin (Ellison): What people are trying to say is that likely, nobody will be working on this, and likely so for the next few years. So unless you volunteer to provide a patch, I recommend to close the issue as "won't fix". Unassigning myself. -- a

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Brian Curtin added the comment: > I thought Python ran everywhere. That's what the documentation says. Python does *run* on Windows (when compiled with Visual Studio or gcc via Cygwin), it just might not be setup to build with the MSYS compiler. -- nosy: +brian.curtin ___

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Martin Ellison added the comment: I thought Python ran everywhere. That's what the documentation says. Regards, Martin (m...@acm.org) On 28 June 2010 21:00, Amaury Forgeot d'Arc wrote: > > Amaury Forgeot d'Arc added the comment: > > I don't think MSYS (or mingw32) is supported at all. > I'm

[issue9098] MSYS build fails with `S_IXGRP' undeclared

Amaury Forgeot d'Arc added the comment: I don't think MSYS (or mingw32) is supported at all. I'm even surprised that the build went so far. -- assignee: -> loewis nosy: +amaury.forgeotdarc, loewis ___ Python tracker

[issue9098] MSYS build fails with `S_IXGRP' undeclared

New submission from Martin Ellison : Python 2.6.5 build fails on MSYS with the following messages mar...@edward /c/Downloads/Python-2.6.5 $ make gcc -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes - I. -IInclude -I./Include -DPy_BUILD_CORE -o Python/import.o Python/i