New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trivial mingw compile fixes #54824
Comments
Some C files fail to compile with mingw, mostly due to missing preprocessor statements:
This patch fixes all the mentioned problems. |
When the patch is applied, what's the resulting status of mingw compilation? |
It compiles all C files which I require. Not sure if this is really *all* C files, but at least very close to all. I will post a list of object files I get on Monday. |
Am 04.12.2010 09:32, schrieb Johann Hanne:
Will it then also link something? |
Sure - it actually builds a python.exe which is fully working for me. If you need a proof, please let me know, I have no problem uploading it somewhere... Is there a reason you are so sceptical? After all, Python for Linux is also usually compiled with gcc, so why shouldn't it work for Win32? |
There is a long track of people contributing patches to Python saying |
Ok, I see. And no, this is *not* my intention. I will post the list of successfully compiled objects files and the linker result on Monday as promised. If it turns out I lied, feel free to put me into the hall of shame. After all, the Win32 platform is not that uncommon. I know, MinGW could be seen as a different platform, but I never encountered a situation where I required anything but the exe file (no special MinGW DLL or something like that). |
Traditionally, MingW-compiled Python binaries would often be |
IMO this is a use case for the new "soabi" tag... |
This is useless, of course. The build must be reproducible.
Your patch does not touch import.c, and the pwd module should probably be removed from a Python running on Windows. |
Unfortunately not: these tags are not supported on Windows. |
|
I don't plan to distribute a MinGW compiled package as an alternative to the official MSVC based build. In my particular use case, I compile everything into a single exe and put the Lib/*.py files into a single zip file. The result is a two-file Python distribution which doesn't need an installation. If somebody is interested, I can elaborate, but this would be off-topic here. As for the reproducibility issue: The configure/Makefile system coming with Python simply doesn't support creating a Windows build. I hope it's clear that the patch is NOT about creating a Windows installer. If this is a requirement for getting my patch in, please let me know so I can stop wasting my time! Whatsoever, if you simply want to reproduce that my compile (!) fixes work, please follow these steps:
|
As promised, here comes the list of modules which successfully compile with MinGW: ./Python-3.1.3/PC/import_nt.o |
Thanks for the explanations! These instructions should be turned into a patch.
|
That's why I was asking what the patch achieves - it was not clear |
|
As I have the feeling that all the discussion (which for the major part I used my spare time already...) is taking too much time, I will stop doing it as part of my job. As I'm privately interested in open source projects, I will continue to have a look at fixing "configure;make" for MinGW; but given my very limited spare time, this might take some weeks... |
Two corrections for the "configure;make" workaround:
|
If that's the objective of the patch, I'm -1 on it.
Well, if MingW could use the VS project files, that would be fine
Understood. Perhaps somebody else is interested in picking up the BTW, you do have your employer's permission to contribute this work, |
bpo-17605 titled "mingw-meta: build interpeter core" was opened on 2013-03-31 so I believe this can be closed as superseded. |
This patch cannot be closed as contain some fixes not reported/proposed yet . |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: