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
Compile error on OS X 10.5 #45699
Comments
Compiling python 2.5.1 on Mac OS X 10.5 (Leopard) fails with the gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp I am also attaching the output of the configuration script. |
Can you please also attach config.log (perhaps compressed)? |
I've attached a compressed config.log. Incidentally, we were able to get Python to compile by appending the
following line to pyconfig.h:
#define SETPGRP_HAVE_ARG -Andres On Oct 29, 2007, at 1:00 PM, Martin v. Löwis wrote:
|
Thanks for testing on Leopard! I haven't gotten that yet. Assigning to Neal since this ought to be fixed before 2.5.2 is released. |
There is an autoconf test that tries to compile | #include <unistd.h> (with many additional defines - see config.log.gz). This file compiles conftest.c:185: error: too many arguments to function 'setpgrp' hence configure concludes that SETPGRP_HAVE_ARG should *not* be defined
Can somebody with access to the system resolve this mystery? Studying |
I don't have access to a 10.5 machine. My guess is that the difference This page talks about needing to include unistd.h, but doesn't give Hopefully someone else with access to 10.5 can confirm if this is the |
It has to do with the MACOSX_DEPLOYMENT_TARGET. If it's set to 10.4, the |
IMO it should be set to 10.4 since we want binaries that run on that |
This issue is fixed in the trunk and python2.5 branch. To work around this issue with the 2.5.1 source tree you have to set ../configure <insert-args-here> MACOSX_DEPLOYMENT_TARGET=10.3 (the value 10.3 is what configure picks by default, building with 10.5 |
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: