Build process not using correct values from Python config Makefile.
-------------------------------------------------------------------

                 Key: MODPYTHON-186
                 URL: http://issues.apache.org/jira/browse/MODPYTHON-186
             Project: mod_python
          Issue Type: Bug
    Affects Versions: 3.2.10, 3.3
            Reporter: Graham Dumpleton
             Fix For: 3.3, 3.2.x


As found by Justin Erenkrantz, the build process for mod_python is using 
LINKFORSHARED from the Python config Makefile. On Mac OS X though this results 
in a expansion of:

LDFLAGS= -Wl,-framework,Python  -u __dummy -u _PyMac_Error -framework System
$(PYTHONFRAMEWORKDIR)/Versions/$(VERSION)/$(PYTHONFRAMEWORK) -framework
CoreServices -framework Foundation   -Wl,-F. -Wl,-F.

where PYTHONFRAMEWORKDIR, VERSION and PYTHONFRAMEWORK aren't defined at the 
point of expansion. Thus the compile executes with options:

.../libtool --silent --mode=link ccache gcc -o mod_python.la  -rpath
.../httpd-trunk/modules -module -avoid-version    hlistobject.lo hlist.lo
filterobject.lo connobject.lo serverobject.lo util.lo tableobject.lo
requestobject.lo _apachemodule.lo mod_python.lo -Wl,-framework,Python -u
__dummy -u _PyMac_Error -framework System /Versions// -framework CoreServices
-framework Foundation -Wl,-F. -Wl,-F. -lm -framework Python -ldl

Ie., '/Versions//' gets passed as an option.

So far this has been working without a problem, but looks like the version of 
gcc which has been supplied with version of XCode distributed around time of 
Apple WWDC in August 06 no longer will accept this and produces the error:

powerpc-apple-darwin8-gcc-4.0.1: /Versions//: No such file or directory

Last known version of gcc to accept it is:

gcc version 4.0.1 (Apple Computer, Inc. build 5341)

Version that no longer accepts it is:

gcc version 4.0.1 (Apple Computer, Inc. build 5363)

Suggestion was that LDSHARED should be used instead of LINKFORSHARED. 
Apparently Subversion had had to address similar problem so can learn from what 
they have done.

Should be fixed for 3.3 and back ported to 3.2.x or we are going to start 
getting a lot of complaints.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to