glib2: configure fails when /usr/bin/python is broken

[faisal.moledina@…]

I get the following error during the configure stage for glib2.

…
checking whether /usr/bin/python version >= 2.5... ./configure: line 7475:  3301 Trace/BPT trap: 5       ( $PYTHON -c "$prog" ) 1>&5 2>&5
configure: error: too old
shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_glib2/glib2/work/glib-2.30.2" && ./configure --prefix=/opt/local --enable-static --disable-dtrace " returned error 133
Error: Target org.macports.configure returned: configure failure: shell command failed (see log for details)
DEBUG: Backtrace: configure failure: shell command failed (see log for details)
    while executing
"$procedure $targetname"
Warning: the following items did not execute (for glib2): org.macports.install org.macports.configure org.macports.build org.macports.destroot
Log for glib2 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_glib2/glib2/main.log
DEBUG: couldn't open "/System/Library/Frameworks/Tcl.framework/Versions/8.5/Resources/tclIndex": no such file or directory
    while executing
"open [file join $dir tclIndex]"
Error: Unable to upgrade port: 1

Attached is the full log of the upgrade.

[faisal.moledina@…]

Installation log

[ryandesign (Ryan Carsten Schmidt)]

It's not too old... it just crashed ("Trace/BPT trap"). Can you find out why? Did a crash log get created? (in /Library/Logs/CrashReporter or ~/Library/Logs/CrashReporter?)

[faisal.moledina@…]

Ah, I see now about the crash. Yes, the crash log is posted ​here. I'm actually getting this Python crash for the System Python almost daily, so I guess it's an issue with my OS X installation. I did not realize that the glib2 port linked to the System Python.

[ryandesign (Ryan Carsten Schmidt)]

Dyld Error Message:
  Library not loaded: /System/Library/Frameworks/Python.framework/Versions/2.7/Python
  Referenced from: /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
  Reason: no suitable image found.  Did find:
        /System/Library/Frameworks/Python.framework/Versions/2.7/Python: file too short
        /Users/faisal/Library/Frameworks/Python.framework/Versions/2.7/Python: stat() failed with errno=13
        /System/Library/Frameworks/Python.framework/Versions/2.7/Python: file too short

Sounds like your /System/Library/Frameworks/Python.framework/Versions/2.7/Python is corrupted. Can you restore it from your backups, or from your OS X installation DVD?

[faisal.moledina@…]

Yep, that was the issue. I grabbed it from another 10.7.2 installation. False alarm about glib2; it upgraded fine now. Thanks for the help.

[ryandesign (Ryan Carsten Schmidt)]

Glad you got it working!