[Pythonmac-SIG] Python 2.3.4 Installation
Samuel M.Smith
smithsm at samuelsmith.org
Mon Sep 27 17:48:17 CEST 2004
I am a little slow here, since the change is to the makefile, do I
remake python 2.3 in order for the patch to work? or is it only going
to be applied when you make a new extension?
On Sep 26, 2004, at 22:19, Bob Ippolito wrote:
> On Sep 27, 2004, at 12:01 AM, Samuel M.Smith wrote:
>
>> There isn't much on the new 2.3.4 Mac Python. Does 2.3.4 fix the
>> problem where you couldn't have
>> any framework version but the one that came with OSX (in this case
>> 2.3 for Panther) ?.
>
> Yes the problem is fixed, but it's still present in the version of
> 2.3.0 that ships with 10.3.. so once you install any other framework
> build of 2.3 in the usual places, it will prevent any extension from
> linking correctly for 2.3.0.
>
> It's possible to monkeypatch Python 2.3.0 so it's not broken in this
> regard, though. Here's a diff:
>
> ---
> /System/Library/Frameworks/Python.framework/Versions/2.3/lib/
> python2.3/config/Makefile Sun Mar 7 22:33:33 2004
> +++ /Users/bob/Makefile Sun Mar 7 22:32:16 2004
> @@ -95,8 +95,8 @@
>
> # Symbols used for using shared libraries
> SO= .so
> -LDSHARED= $(CC) $(LDFLAGS) -bundle -framework $(PYTHONFRAMEWORK)
> -BLDSHARED= $(CC) $(LDFLAGS) -bundle -framework $(PYTHONFRAMEWORK)
> +LDSHARED= $(CC) $(LDFLAGS) -bundle -undefined dynamic_lookup
> +BLDSHARED= $(CC) $(LDFLAGS) -bundle -undefined dynamic_lookup
> DESTSHARED= $(BINLIBDEST)/lib-dynload
>
> # Executable suffix (.exe on Windows and Mac OS X)
>
More information about the Pythonmac-SIG
mailing list