Compiling python 2.5.1 on Mac OS X 10.5 (Leopard) fails with the
following message:

gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp
-mno-fused-madd -DNDEBUG -g -O3 -Wall -Wstrict-prototypes  -I.
-I./Include   -DPy_BUILD_CORE  -c ./Modules/posixmodule.c -o
Modules/posixmodule.o
./Modules/posixmodule.c: In function ‘posix_setpgrp’:
./Modules/posixmodule.c:3592: error: too few arguments to function ‘setpgrp’
make: *** [Modules/posixmodule.o] Error 1

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:

>
> Martin v. Löwis added the comment:
>
> Can you please also attach config.log (perhaps compressed)?
>
> ----------
> nosy: +loewis
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1358>
> __________________________________

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.
 (But someone needs to come up with a proper patch.)

There is an autoconf test that tries to compile

| #include <unistd.h>
| int
| main ()
| {
| setpgrp(0,0);
|   ;
|   return 0;
| }

(with many additional defines - see config.log.gz). This file compiles
with the error message

conftest.c:185: error: too many arguments to function 'setpgrp'

hence configure concludes that SETPGRP_HAVE_ARG should *not* be defined
- yet you say it works when it is defined.

Can somebody with access to the system resolve this mystery? Studying
the header file that has the setpgrp declaration is probably necessary.

I don't have access to a 10.5 machine.  My guess is that the difference
is between configure not setting _XOPEN_SOURCE and/or
_XOPEN_SOURCE_EXTENDED and it being set in pyconfig.h.  At least those
are both defined on 10.4.  

This page talks about needing to include unistd.h, but doesn't give
enough info:
http://developer.apple.com/documentation/Darwin/Reference/Manpages/man2/setpgid.2.html

Hopefully someone else with access to 10.5 can confirm if this is the
case and we can resolve this.

It has to do with the MACOSX_DEPLOYMENT_TARGET. If it's set to 10.4, the 
legacy version of setpgrp is used (with args), it it's 10.5, setpgrp 
expects no arguments. It seems configure won't detect the difference.

IMO it should be set to 10.4 since we want binaries that run on that
platform too.  Is this something we can fix in the configure script?

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 
MACOSX_DEPLOYMENT_TARGET when configuring python:

  ../configure <insert-args-here> MACOSX_DEPLOYMENT_TARGET=10.3

(the value 10.3 is what configure picks by default, building with 10.5 
as the target works as well). The problem is that configure picked a 
deployment target for use during compilation of python itself, but 
didn't use that during the configure phase. That causes configure to 
pick up the wrong set of feature macros.