BUG: port build python24 fails on i386

[n4hy@…]

port install libtool needed by other things went perfectly. port install python24 fails with the error message:

mac1:/usr/local/bin root# port -f install python24 ---> Building python24 with target all Error: Target com.apple.build returned: shell command "cd "/opt/local/var/db/dports/build/_opt_local_etc_ports_dports_lang_python24/work/Python-2.4.2" && make all" returned error 2 Command output: /usr/bin/install -c -d -m 755 Python.framework/Versions/2.4 libtool -o Python.framework/Versions/2.4/Python -dynamic libpython2.4.a \

-lSystem -lSystemStubs -arch_only ppc -install_name /opt/local/Library/Frameworks/Python.framework/Versions/2.4/Python -compatibility_version 2.4 -current_version 2.4

libtool: unrecognized option `-o' Try `libtool --help' for more information. make: * [Python.framework/Versions/2.4/Python] Error 1

Error: Status 1 encountered during processing.

[aschenke@…]

The current python24 (2.4.3) installs OK for me on Mac OS X 10.4 (Darwin 8.6.0). Since you're on a PC, have you tried installing the darwin_i386 or puredarwin variants? It looks like you're set up to compile Mac OS PowerPC frameworks.

General question: Is DarwinPorts officially supported on Linux?

(Added maintainer as CC)

[mww@…]

in a perfect world(tm), the darwin_i386 variant should be chosen automatically for you; but please have a try with the puredarwin version - I have to blind-debug this issue as I do not have access to a i386-mac.

btw. Linux is not an officially supported platform though port itself should work there, too.

[n4hy@…]

Thanks for your recent note. I do not understand the relevance of your remarks to my issue. I see that port build python24 fails on i386 is the Summary. I do not know how this summary became attached. My issue is completely and totally on my Mac dual G5 machine. It is running the latest dport, the latest OSX, and gcc 4.1.0. I went to the python.org page and received the dmg and it installs 2.4.3 perfectly and works.

Bob McGwier

[aschenke@…]

This report has Hardware=PC and OS=Linux, so we thought you were running on an i386 machine. Does it still give you the same error when you try to install it with DP? What message do you get if you enter:

libtool -V

in the Terminal?

[arthur@…]

Is this bug still open? I've just had the same problem when trying to upgrade python24

rode:~ 442: uname -a Darwin rode.york.ac.uk 8.7.0 Darwin Kernel Version 8.7.0: Fri May 26 15:20:53 PDT 2006; root:xnu-792.6.76.obj~1/RELEASE_PPC Power Macintosh powerpc

rode:~ 443: port installed|grep python24 port lis python24 2.4.2_3+darwin_8+macosx (active) rode:~ 444: port list|grep python24 python24 lang/python24 2.4.3 An interpreted, object-oriented programming language

rode:file._opt_local_var_db_dports_sources_rsync.rsync.opendarwin.org_dpupdate_dports_lang_python24/work/Python-2.4.3 403: make all 14:13:56 /usr/bin/install -c -d -m 755 Python.framework/Versions/2.4 install: chmod 755 Python.framework/Versions/2.4: Operation not permitted libtool -o Python.framework/Versions/2.4/Python -dynamic libpython2.4.a \

-lcc_dynamic -lSystem -lSystemStubs -arch_only ppc -install_name /opt/local/Library/Frameworks/Python.framework/Versions/2.4/Python -compatibility_version 2.4 -current_version 2.4

libtool: unrecognized option `-o' Try `libtool --help' for more information. make: * [Python.framework/Versions/2.4/Python] Error 1

[arthur@…]

Update: specifying /usr/bin/libtool explicitly rather than picking up /opt/local/bin/libtool (which is first in my path) fixes the problem.

[aschenke@…]

I just installed the current version (python24 @2.4.3_1+darwin_8) on Intel with no problems.

It looks like you're running on a PowerPC Mac; if this is correct, then you may want to open a new ticket since this one deals specifically with problems on Intel-based systems. Before you do, try doing an uninstall and then re-install of python, rather than using "upgrade".

[markd@…]

There shouldn't be a /opt/local/bin/libtool. The libtool port installs /opt/local/bin/glibtool. Sounds like you've installed it manually in the MacPorts tree. I think this can be closed.