This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients eduardocereto, eric.araujo, ned.deily, ronaldoussoren, samueljohn
Date 2013-07-06.15:25:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373124314.71.0.615332721625.issue11445@psf.upfronthosting.co.za>
In-reply-to
Content
I've attached an updated patch (against the 2.7 branch, the same idea should work for 3.3 and default). 

This does two things:

1) Explicity add '-Wl,-search_paths_first' to LDFLAGS on Mac OS X.

   This ensures that the linker behaves like other platforms: in every
   directory on the search path look for both shared and static libraries,
   the default (upto xcode 4) was to first walk the entire path looking
   for dylibs, then walk the path again looking for static libraries.

2) Change the order of arguments when linking $(BUILDPYTHON),
   the -L flags in $(LDFLAGS) were first added before the "-L." flag, 
   and are now after that flag. This ensures that the correct python 
   library will be found, even if there is a libpython in one of the
   directories on the search path that's added by $(LDFLAGS).

This should work fine on OSX (obviously) and Linux, but I'm not 100% that
moving $(LDFLAGS) will work with the vendor compilers on commercial unix
systems.

(Adding 3.3 and 3.4 to the versions because those should also be affected by this issue)
History
Date User Action Args
2013-07-06 15:25:16ronaldoussorensetrecipients: + ronaldoussoren, ned.deily, eric.araujo, samueljohn, eduardocereto
2013-07-06 15:25:14ronaldoussorensetmessageid: <1373124314.71.0.615332721625.issue11445@psf.upfronthosting.co.za>
2013-07-06 15:25:14ronaldoussorenlinkissue11445 messages
2013-07-06 15:25:14ronaldoussorencreate