On Sun, 17 Mar 2013, Barry Smith wrote: > > We should support the Msys interface, what stands in the way of it.
Ok - msys appears to be part of mingw - and multiple sources of instalation information. http://www.mingw.org/wiki/Getting_Started Installed via 'Graphical User Interface Installer' instructions with 'mingw-get-inst' But I don't see any python. ['mingw-get list python' - the recommended package manager gives 'unknown package' errork] Ok - attempt to build from sources - but I get error here aswell. gcc -pthread -c -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -DPy_BUILD_CORE -o Python/import.o Python/import.c Python/import.c: In function 'write_compiled_module': Python/import.c:886:50: error: 'S_IXGRP' undeclared (first use in this function) Python/import.c:886:50: note: each undeclared identifier is reported only once for each function it appears in Python/import.c:886:61: error: 'S_IXOTH' undeclared (first use in this function) make: *** [Python/import.o] Error 1 Google 'msys python' gives http://opensourcepack.blogspot.com/2012/04/its-just-wrong-msys-python.html Is this hacked python one uses for msys? I don't know.. There are also references to windows native python - but then - petsc configure doesn't work with it. Also - I don't see any editors [vi/emacs] in msys - presumably one is expected to use MS native mostly [including for python?] Satish
