I downloaded Python-2.4.2.tgz expanded it into the directory
Python-2.4.2
I cd in python-2.4.2 and run
./configure --enable--framework
make
this creates a file in the python-2.4.2 directory called python.exe
if I run
./python.exe
I get the following prompt
Python 2.4.1 (#2, Mar 31 2005, 00:05:1
On 08 Jan, 2006, at 21:32, Samuel M. Smith wrote:
> I downloaded Python-2.4.2.tgz expanded it into the directory
> Python-2.4.2
> I cd in python-2.4.2 and run
>
> ./configure --enable--framework
> make
excuse the typo here I actually ran
./configure --enable-framework
I have os x 10.4.3 I had p
On Jan 8, 2006, at 8:44 PM, Samuel M. Smith wrote:
>
> On 08 Jan, 2006, at 21:32, Samuel M. Smith wrote:
>
>> I downloaded Python-2.4.2.tgz expanded it into the directory
>> Python-2.4.2
>> I cd in python-2.4.2 and run
>>
>> ./configure --enable--framework
>> make
>
> excuse the typo here I actua
I next tried removing the old 2.4.1 installation by changing the name
of the directory
/library/frameworks/python.framework/versions/2.4 to 2.4a
I then did a ./configure and make
I tried to run ./python.exe and got the following error
AlBook:/install/python/macpython/python2.4.2/python-2.4.2 smi
>
> You did get 2.4.2, but it's dynamically linking to /Library/
> Frameworks/Python.framework because that's where it's going to
> install to.
>
> try this:
>
> env DYLD_FRAMEWORK_PATH=. ./python.exe
>
but shouldn't that dynamic link have been obviated once I did a
sudo make install? At that poi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Samuel M. Smith wrote:
> I next tried removing the old 2.4.1 installation by changing the name
> of the directory
> /library/frameworks/python.framework/versions/2.4 to 2.4a
>
> I then did a ./configure and make
> I tried to run ./python.exe and got
On Jan 8, 2006, at 9:29 PM, Kevin Walzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Samuel M. Smith wrote:
>> I next tried removing the old 2.4.1 installation by changing the name
>> of the directory
>> /library/frameworks/python.framework/versions/2.4 to 2.4a
>>
>> I then did a
>>
> Aren't the instructions about the "makeframework install" somewhere in
> the Python source tree (a README or something like that)? I remember
> running into this issue with 2.4.2, then consulting docs somewhere in
> the code package I downloaded, then trying again successfully. The
> buildd pr
