py-pyqt4: qtdirs.app/Contents/MacOS/qtdirs failed to create qtdirs.out. Make sure configure your Qt installation is correct.

[cgcgcg@…]

i get an error when i try to install py27-pyqt4, after installing qt4-mac:

:info:configure import cStringIO # dynamically loaded from /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-dynload/cStringIO.so
:info:configure Error: qtdirs.app/Contents/MacOS/qtdirs failed to create qtdirs.out. Make sure
:info:configure your Qt installation is correct.

main.log as attachment

[cgcgcg@…]

Log file after adding 'python.bin-append -v -v' to Portfile

[michaelld (Michael Dickens)]

Comparing the log output and the Python configure script used by PyQt4, a Qt-based c++ file was successfully compiled and executed, but it seems like it (via Qt4 internally) failed to either (1) create the named output file that it uses to glean internal info from QMake; or (2) the named output file was not created in the correct location. Quite strange.

Have you tried:

sudo port clean py27-pyqt4

and then installing / upgrading again? Do you get the same error?

[cgcgcg@…]

yes, i did sudo port clean py27-pyqt4 and installed again with the same Error

[michaelld (Michael Dickens)]

OK. Can you try the following:

cd `port dir py27-pyqt4`/work/PyQt-mac-gpl-4.9.6
ls -lAF qtdirs.*

What does this last command return? If the file "qtdirs.out" is there, can you attach it to this ticket?

[cgcgcg@…]

thanks, the output of ls -lAF qtdirs.* is:

-rw-r--r-- 1 macports admin 2469 30 Dez 19:23 qtdirs.cpp

-rw-r--r-- 1 macports admin 10267 30 Dez 19:23 qtdirs.mk

-rw------- 1 macports admin 3792 30 Dez 19:23 qtdirs.o

-rw-r--r-- 1 macports admin 174 30 Dez 19:23 qtdirs.pro

qtdirs.app: total 0 drwxr-xr-x 6 macports admin 204 30 Dez 19:23 Contents/

[michaelld (Michael Dickens)]

Interesting. Please attach the file "qtdirs.mk". Then, do from that some directory:

sudo chmod -R a+rw .
qtdirs.app/Contents/MacOS/qtdirs

and report what the last command prints out (if anything); and, whether or not the file "qtdirs.out" was created by it.

[michaelld (Michael Dickens)]

Hadn't seen the attaches zip archive. When I run the executable ("qtdirs.app/Contents/MacOS/qtdirs"), it runs without error and produces the following (in the form of the file "qtdirs.out"):

/opt/local
/opt/local/include
/opt/local/lib
/opt/local/Library/Frameworks
/opt/local/bin
/opt/local/share/qt4
/opt/local/share/qt4/plugins
264196
1048575
Open Source
shared
PyQt_NoPrintRangeBug

which is identical to that produced by my local build of py27-pyqt4.

[cgcgcg@…]

did: sudo chmod -R a+rw .
running qtdirs.app/Contents/MacOS/qtdirs
give me:
Segmentation fault: 11

new install on another mac mini with fresh mountain lion is running without errors. thank you for youre good work

[michaelld (Michael Dickens)]

OK; glad it's working on another computer. Do you still want to keep poking on this issue?

If so, what does

otool -L qtdirs.app/Contents/MacOS/qtdirs

return.

And, again, could you attach the file "qtdirs.mk"?

[cgcgcg@…]

otool -L qtdirs.app/Contents/MacOS/qtdirs
qtdirs.app/Contents/MacOS/qtdirs:

/opt/local/Library/Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)

[michaelld (Michael Dickens)]

I'm guessing this has something to do with clang optimization on 10.7; maybe. What does "/usr/bin/clang -v" return?

If you do the following:

sed -e "s@-O2 @@g" mkdirs.mk > mkdirs2.mk
make -f mkdirs2.mk
qtdirs.app/Contents/MacOS/qtdirs

does this last step work? If so, can you attach the "qtdirs.mk" and "qtdirs.out"?

[cgcgcg@…]

/usr/bin/clang -v
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix
sed -e "s@-O2 @@g" mkdirs.mk > mkdirs2.mk
sed: mkdirs.mk: No such file or directory

should it be in:
cd port dir py27-pyqt4/work/PyQt-mac-gpl-4.9.6
¿

[michaelld (Michael Dickens)]

Yes; the "sed" commands are in the PyQt-mac-gpl-4.9.6, executed -after- you've encountered the error.

What does "xcodebuild -version" return?

Have you considered updating your Xcode install?

[cgcgcg@…]

Xcode 4.5.1
Build version 4G1004

updating xcode to 4.5.2 -> takes some time because of lame dsl, sorry

then i will try to install again and do the sed-thing if errors happen

[michaelld (Michael Dickens)]

Sorry about the lame DSL download; yes, Xcode is pretty big and slow downloads suck. I leave mine on overnight to get it downloaded -- slow cable.

Arg. I guess that Xcode installs differently on different Mac OS versions? I've heard of this before. On my 10.8 box, Xcode 4.5.2 installs "Apple clang version 4.1 (tags/Apple/clang-421.11.65) (based on LLVM 3.1svn)". On your 10.7 box, Xcode 4.5.1 seems to be installing "Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)"; Xcode 4.5.2 maybe will install some more recently version of clang? When you do get it the newer Xcode installed, please reply back here with what the following return:

/usr/bin/clang -v
xcodebuild -version
uname -a

I think the solution here is in qt4-mac, to ban clang < 3.1 correctly (the Portfile already has a comment to this effect, but clearly the implementation didn't work for you). Please do try the "sed" stuff when you get a chance; if that works, then it's a clang optimization issue. If it doesn't work, then we'll try something else.

If you want to try something else immediately, you can install qt4-mac differently (with your favorite variants):

sudo port uninstall qt4-mac
sudo port install qt4-mac configure.compiler=llvm-gcc-4.2

[cgcgcg@…]

ok, did:

• new xcode installed
• sudo port selfupdate
• sudo port upgrade outdated
• sudo port clean py27-pyqt4
• sudo port install py27-pyqt4
• Error: Processing of port py27-pyqt4 failed
• cd port dir py27-pyqt4/work/PyQt-mac-gpl-4.9.6
• sed -e "s@-O2 @@g" mkdirs.mk > mkdirs2.mk
  sed: mkdirs.mk: No such file or directory
• mkdirs2.mk is empty file
• qtdirs.mk is the same like the attached except creation date in line 3
• qtdirs.out, no such file

[cgcgcg@…]

xcode update was only about 120mb
clang still 2.1 --> Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn) Target: x86_64-apple-darwin11.4.2 Thread model: posix
xcodebuild -version --> Xcode 4.5.2 Build version 4G2008a
uname -a --> Darwin PepBook-2.local 11.4.2 Darwin Kernel Version 11.4.2: Thu Aug 23 16:25:48 PDT 2012; root:xnu-1699.32.7~1/RELEASE_X86_64 x86_64

[michaelld (Michael Dickens)]

Thanks for the info on the update. My bad; the sed stuff should read:

sed -e "s@-O2 @@g" qtdirs.mk > qtdirs2.mk
make -f qtdirs2.mk
qtdirs.app/Contents/MacOS/qtdirs

[cgcgcg@…]

sudo port install qt4-mac configure.compiler=llvm-gcc-4.2 has installed fine
port install py27-pyqt4 gave the same error:

:info:configure Error: qtdirs.app/Contents/MacOS/qtdirs failed to create qtdirs.out. Make sure
:info:configure your Qt installation is correct.

in /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/main.log

sed --> ah, ok, thank you

sed -e "s@-O2 @@g" qtdirs.mk > qtdirs2.mk
make -f qtdirs2.mk
make: Nothing to be done for `first'.
qtdirs.app/Contents/MacOS/qtdirs
Segmentation fault: 11

attached /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/work/PyQt-mac-gpl-4.9.6/qtdirs2.mk

[michaelld (Michael Dickens)]

Yes; OK; interesting. Maybe something else is going on than what I suspect. Can you post the new "qtdirs.mk" file?

Then do:

rm -rf qtdirs.app qtdirs.o
make -f qtdirs2.mk
qtdirs.app/Contents/MacOS/qtdirs

[cgcgcg@…]

out for an hour, then i will try, thank you

[cgcgcg@…]

sh-3.2# rm -rf qtdirs.app qtdirs.o
sh-3.2# make -f qtdirs2.mk
/usr/bin/clang++ -c -pipe -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -Wall -W -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED -I/opt/local/share/qt4/mkspecs/macx-g++ -I. -I. -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/include -F/opt/local/Library/Frameworks -F/opt/local/lib -o qtdirs.o qtdirs.cpp
/usr/bin/clang++ -headerpad_max_install_names -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -o qtdirs.app/Contents/MacOS/qtdirs qtdirs.o   -F/opt/local/Library/Frameworks -F/opt/local/lib  -F/opt/local/Library/Frameworks -F/opt/local/lib -L/opt/local/lib -framework QtCore 
sh-3.2# qtdirs.app/Contents/MacOS/qtdirs
Segmentation fault: 11

[michaelld (Michael Dickens)]

Quite strange. Here's another test:

sed -e "s@clang@g@g" qtdirs.mk > qtdirs3.mk
rm -rf qtdirs.app qtdirs.o
make -f qtdirs2.mk
qtdirs.app/Contents/MacOS/qtdirs

[cgcgcg@…]

sorry

sh-3.2# sed -e "s@clang@g@g" qtdirs.mk > qtdirs3.mk
sh-3.2# rm -rf qtdirs.app qtdirs.o
sh-3.2# make -f qtdirs3.mk
/usr/bin/g++ -c -pipe -O2 -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -Wall -W -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED -I/opt/local/share/qt4/mkspecs/macx-g++ -I. -I. -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/include -F/opt/local/Library/Frameworks -F/opt/local/lib -o qtdirs.o qtdirs.cpp
/usr/bin/g++ -headerpad_max_install_names -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -o qtdirs.app/Contents/MacOS/qtdirs qtdirs.o   -F/opt/local/Library/Frameworks -F/opt/local/lib  -F/opt/local/Library/Frameworks -F/opt/local/lib -L/opt/local/lib -framework QtCore 
sh-3.2# qtdirs.app/Contents/MacOS/qtdirs
Segmentation fault: 11

attached crash log

[michaelld (Michael Dickens)]

Well, this is perplexing. Do you have anything related to Qt4 installed into /usr/local, /sw, or /Library/Frameworks (or, elsewhere) that you know of? For example, Qt's binaries install into /Library/Frameworks/Qt*. I sometimes use /usr/local as an alternative testing site for my programs, to see if pre-installed stuff gets found by a new build (e.g., within MacPorts). /sw was used by Fink; I assume it still is.

Here's another test, which maybe will provide more info in the crash log:

sed -e "s@-O2@-g@g" qtdirs.mk > qtdirs4.mk
rm -rf qtdirs.app qtdirs.o
make -f qtdirs4.mk
qtdirs.app/Contents/MacOS/qtdirs

and, then, I think it's about time to rebuild qt4-mac with gcc:

sudo port uninstall qt4-mac
sudo port install qt4-mac configure.compiler=llvm-gcc-4.2

and, add any variants you want/need between "qt4-mac" and "configure". Then, once this is installed:

sudo port clean py27-pyqt4
sudo port install py27-pyqt4

should succeed; if not, we'll keep poking on this!

[cgcgcg@…]

i did a failed install from a package but then restored from time maschine
could not find any other qt4 installation.

cd /usr/local
ls
MacGPG2	bin	doc	etc	include	lib	sbin	share
ls etc
sane.d
ls bin
bbdiff			dftest			gitx			idl2wrs			rawshark		rtl_sdr			sane-find-scanner	wireshark
bbedit			dumpcap			gpg			libusb-config		rtl_adsb		rtl_tcp			scanimage
bbfind			editcap			gpg-agent		mergecap		rtl_eeprom		rtl_test		text2pcap
capinfos		gamma4scanimage		gpg2			randpkt			rtl_fm			sane-config		tshark
ls /usr/local/sbin
saned
ls /usr/local/include
osxfuse			rtl-sdr.h		rtl-sdr_export.h	sane			usb.h			usbpp.h
ls /usr/local/lib
libfuse.0.dylib			libmacfuse_i64.2.dylib		libosxfuse_i32.2.dylib		librtlsdr.0.0.0.dylib		libusb-0.1.4.4.5.dylib		libusbpp.a
libfuse.2.dylib			libmacfuse_i64.dylib		libosxfuse_i32.dylib		librtlsdr.0.dylib		libusb-0.1.4.dylib		libusbpp.dylib
libfuse.dylib			libosxfuse.2.7.3.dylib		libosxfuse_i32.la		librtlsdr.a			libusb.a			libusbpp.la
libfuse_ino64.2.dylib		libosxfuse.2.dylib		libosxfuse_i64.2.7.3.dylib	librtlsdr.dylib			libusb.dylib			pkgconfig
libfuse_ino64.dylib		libosxfuse.dylib		libosxfuse_i64.2.dylib		libsane.1.dylib			libusb.la			sane
libmacfuse_i32.2.dylib		libosxfuse.la			libosxfuse_i64.dylib		libsane.dylib			libusbpp-0.1.4.4.5.dylib
libmacfuse_i32.dylib		libosxfuse_i32.2.7.3.dylib	libosxfuse_i64.la		libsane.la			libusbpp-0.1.4.dylib
ls /usr/local/share
locale	man	mplayer	sane
cd /sw
-bash: cd: /sw: No such file or directory
cd /Library/Frameworks/qt*
-bash: cd: /Library/Frameworks/qt*: No such file or directory
cd /Library/Frameworks
ls
AEProfiling.framework		AudioMixEngine.framework	OSXFUSE.framework		iLifeKit.framework		iLifeSlideshow.framework	iTunesLibrary.framework
AERegistration.framework	MacFUSE.framework		PluginManager.framework		iLifePageLayout.framework	iODBC.framework
Adobe AIR.framework		NyxAudioAnalysis.framework	iLifeFaceRecognition.framework	iLifeSQLAccess.framework	iODBCinst.framework	

then

sh-3.2# sed -e "s@-O2@-g@g" qtdirs.mk > qtdirs4.mk
sh-3.2# rm -rf qtdirs.app qtdirs.o
sh-3.2# make -f qtdirs4.mk
/usr/bin/clang++ -c -pipe -g -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -Wall -W -DQT_NO_DEBUG -DQT_CORE_LIB -DQT_SHARED -I/opt/local/share/qt4/mkspecs/macx-g++ -I. -I. -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/Library/Frameworks/QtCore.framework/Versions/4/Headers -I/opt/local/include -F/opt/local/Library/Frameworks -F/opt/local/lib -o qtdirs.o qtdirs.cpp
/usr/bin/clang++ -headerpad_max_install_names -arch x86_64 -Xarch_x86_64 -mmacosx-version-min=10.7 -o qtdirs.app/Contents/MacOS/qtdirs qtdirs.o   -F/opt/local/Library/Frameworks -F/opt/local/lib  -F/opt/local/Library/Frameworks -F/opt/local/lib -L/opt/local/lib -framework QtCore 
sh-3.2# qtdirs.app/Contents/MacOS/qtdirs
Segmentation fault: 11

crashlog attached qtdirs4.mk attached

sh-3.2# port install py27-pyqt4
--->  Computing dependencies for py27-pyqt4
--->  Fetching archive for py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/py27-pyqt4
--->  Fetching distfiles for py27-pyqt4
--->  Verifying checksum(s) for py27-pyqt4
--->  Extracting py27-pyqt4
--->  Applying patches to py27-pyqt4
--->  Configuring py27-pyqt4
Error: org.macports.configure for port py27-pyqt4 returned: configure failure: command execution failed
Please see the log file for port py27-pyqt4 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py27-pyqt4 failed

/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/main.log attached

[michaelld (Michael Dickens)]

Wow; thanks! That's very thorough. It looks like qt4-mac is what is messing up; the method "QIconvCodec::createIconv_t" is calling 0 for some reason. I would tend to believe that fully reinstalling it, from source, is the right way to go. I just checked in r101393, which blocks clang on 10.7; so, in something like 30 minutes this revision will become "live", and I'd recommend you do:

sudo port selfupdate
ff=`port installed qt4-mac | sed -e 1d -e "s@(active)@@g"`
sudo port -f uninstall $ff
sudo port -s install qt4-mac

and, add what variants you wish to this last command. Assuming it succeeds, then again try:

sudo port clean py27-pyqt4
sudo port install py27-pyqt4

and hopefully this time it will work.

[michaelld (Michael Dickens)]

Also, I believe when you download a new Xcode.app, you have to manually install the new command line tools. You start Xcode running, then go into Preferences, Downloads, Components. Click on "Check and Install Now" to retrieve the latest versions of everything. Then, for the "Command Line Tools" if there is an "Install" button click that. Eventually, updated command line tools will be installed. From what I understand, clang will be updated to "Apple clang version 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn)". Which in theory should work to compile qt4-mac but does not seem to. Hence, why I've blocked using it -- no Apple clang on 10.7 or older.

[michaelld (Michael Dickens)]

To the OP: Please do the command line tools install as I write in the previous entry. After it is done, re-do "/usr/bin/clang++ -v" and please report what it returns.

I'm wondering if on the "Downloads" tab of the Xcode.app Preferences, the checkbox for ""Check for and install updates automatically" was checked? It was not for me, and hence my command line tools had to be updated manually (by me). I recommend checking that box and allowing Xcode to do what it needs to do.

[cgcgcg@…]

wow, thank you!

it takes a bit

[cgcgcg@…]

/usr/bin/clang++ -v
Apple clang version 2.1 (tags/Apple/clang-163.7.1) (based on LLVM 3.0svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix

manually upgraded command line Tools, then

/usr/bin/clang++ -v
Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin11.4.2
Thread model: posix

k, clang updated, then reinstalled qt4-mac

PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ sudo port selfupdate
Password:
--->  Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.2 downloaded.
--->  Updating the ports tree
--->  MacPorts base is already the latest version

The ports tree has been updated. To upgrade your installed ports, you should run
  port upgrade outdated
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ port upgrade outdated
Error: Insufficient privileges to write to MacPorts install prefix.
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ sudo port upgrade outdated
--->  Fetching archive for libnet11
--->  Attempting to fetch libnet11-1.1.6_2.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libnet11
--->  Attempting to fetch libnet11-1.1.6_2.darwin_11.x86_64.tbz2.rmd160 from http://mse.uk.packages.macports.org/sites/packages.macports.org/libnet11
--->  Installing libnet11 @1.1.6_2
--->  Cleaning libnet11
--->  Deactivating libnet11 @1.1.6_1
--->  Cleaning libnet11
--->  Activating libnet11 @1.1.6_2
--->  Cleaning libnet11
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ ff=`port installed qt4-mac | sed -e 1d -e "s@(active)@@g"`
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ sudo port -f uninstall $ff
--->  Deactivating qt4-mac @4.8.4_2+quartz
--->  Cleaning qt4-mac
--->  Uninstalling qt4-mac @4.8.4_2+quartz
--->  Cleaning qt4-mac
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ sudo port -s install qt4-mac
--->  Computing dependencies for qt4-mac
--->  Fetching distfiles for qt4-mac
--->  Attempting to fetch qt-everywhere-opensource-src-4.8.4.tar.gz from http://get.qt.nokia.com/qt/source/
--->  Attempting to fetch qt-everywhere-opensource-src-4.8.4.tar.gz from http://mse.uk.distfiles.macports.org/sites/distfiles.macports.org/qt4-mac
--->  Verifying checksum(s) for qt4-mac
--->  Extracting qt4-mac
--->  Applying patches to qt4-mac
--->  Configuring qt4-mac
--->  Building qt4-mac
--->  Staging qt4-mac into destroot
--->  Installing qt4-mac @4.8.4_2
--->  Activating qt4-mac @4.8.4_2
--->  Cleaning qt4-mac
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.
PepBook-2:PyQt-mac-gpl-4.9.6 christoph$ sudo port clean py27-pyqt4
Password:
--->  Cleaning py27-pyqt4
PepBook-2:/ christoph$ su
Password:
sh-3.2# port install py27-pyqt4
--->  Computing dependencies for py27-pyqt4
--->  Fetching archive for py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://packages.macports.org/py27-pyqt4
--->  Attempting to fetch py27-pyqt4-4.9.6_1.darwin_11.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/py27-pyqt4
--->  Fetching distfiles for py27-pyqt4
--->  Verifying checksum(s) for py27-pyqt4
--->  Extracting py27-pyqt4
--->  Applying patches to py27-pyqt4
--->  Configuring py27-pyqt4
Error: org.macports.configure for port py27-pyqt4 returned: configure failure: command execution failed
Please see the log file for port py27-pyqt4 for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/main.log
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets
Error: Processing of port py27-pyqt4 failed
sh-3.2# cd /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/
sh-3.2# open .
sh-3.2# ls
main.log
sh-3.2# cd `port dir py27-pyqt4`/work/PyQt-mac-gpl-4.9.6
sh-3.2# qtdirs.app/Contents/MacOS/qtdirs
Segmentation fault: 11

close but no cigar

[michaelld (Michael Dickens)]

Wow. This is a nasty bug, very difficult to track down! We'll keep poking at it. What do the following return:

otool -L /opt/local/Library/Frameworks/QtCore.framework/QtCore
port installed | grep active

It might also be useful to Qt4 installed for debug:

sudo port -k install qt4-mac +debug
sudo port clean py27-pyqt4
sudo port install py27-pyqt4

and, this last should error out again. But, now we -might- be able to do some debugging of the application:

cd `port dir py27-pyqt4`/work/PyQt-mac-gpl-4.9.6
gdb qtdirs.app/Contents/MacOS/qtdirs

and, once that it loaded, in gdb do "r" (and return). It should error out, and then you can do "bt" to get the backtrace, which is sort of like the crash report.

[cgcgcg@…]

sh-3.2# otool -L /opt/local/Library/Frameworks/QtCore.framework/QtCore
/opt/local/Library/Frameworks/QtCore.framework/QtCore:
	/opt/local/Library/Frameworks/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.7)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)
	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 41.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 635.21.0)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 55148.1.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 52.0.0)
	/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 53.0.0)
sh-3.2# port installed | grep active
  arpwatch @2.1a15_2 (active)
  atk @2.6.0_0 (active)
  autoconf @2.69_0 (active)
  automake @1.13.1_0 (active)
  boost @1.52.0_1+no_single+no_static+python27 (active)
  bzip2 @1.0.6_0 (active)
  cairo @1.12.8_2+x11 (active)
  cmake @2.8.10_1 (active)
  cppunit @1.12.1_0 (active)
  db46 @4.6.21_7 (active)
  dbus @1.6.8_0+startupitem (active)
  ettercap-ng @0.7.3_5 (active)
  expat @2.1.0_0 (active)
  fftw-3 @3.3.3_0 (active)
  fftw-3-single @3.3.3_0 (active)
  file @5.11_0 (active)
  flac @1.2.1_1 (active)
  fontconfig @2.10.2_0 (active)
  freetype @2.4.10_0 (active)
  gdbm @1.10_2 (active)
  gdk-pixbuf2 @2.26.5_1+x11 (active)
  gettext @0.18.2_0 (active)
  ghostscript @9.06_1 (active)
  glib2 @2.34.3_0 (active)
  gnutls @2.12.19_0 (active)
  gobject-introspection @1.34.1.1_2 (active)
  gperf @3.0.4_2 (active)
  gtk2 @2.24.14_1+x11 (active)
  help2man @1.40.13_0 (active)
  hicolor-icon-theme @0.12_0 (active)
  icu @49.1.2_0 (active)
  ImageMagick @6.8.0-7_0+q16 (active)
  jasper @1.900.1_9 (active)
  jbig2dec @0.11_1 (active)
  jpeg @8d_0 (active)
  lame @3.99.5_0 (active)
  lcms @1.19_2 (active)
  lcms2 @2.4_0 (active)
  lftp @4.3.8_0 (active)
  libedit @20121213-3.0_0 (active)
  libffi @3.0.11_1 (active)
  libgcrypt @1.5.0_0 (active)
  libglade2 @2.6.4_6 (active)
  libgpg-error @1.10_0 (active)
  libiconv @1.14_0 (active)
  libid3tag @0.15.1b_2 (active)
  libidn @1.25_0 (active)
  libmad @0.15.1b_3 (active)
  libmng @1.0.10_2 (active)
  libnet11 @1.1.6_2 (active)
  libogg @1.3.0_1 (active)
  libpaper @1.1.24_0 (active)
  libpcap @1.3.0_0 (active)
  libpixman @0.28.2_0 (active)
  libpng @1.5.13_0 (active)
  libsndfile @1.0.25_0 (active)
  libtasn1 @2.11_0 (active)
  libtool @2.4.2_3 (active)
  libusb @1.0.9_0 (active)
  libvorbis @1.3.3_0 (active)
  libxml2 @2.8.0_0 (active)
  libxslt @1.1.27_0 (active)
  logwatch @7.3.6_2 (active)
  lzo2 @2.05_1 (active)
  m4 @1.4.16_0 (active)
  ncurses @5.9_1 (active)
  ncursesw @5.8_0 (active)
  nosetests_select @0.1_0 (active)
  opencore-amr @0.1.3_0 (active)
  openssl @1.0.1c_0 (active)
  p5.12-locale-gettext @1.50.0_7 (active)
  p7zip @9.20.1_1 (active)
  pango @1.30.1_3+x11 (active)
  pcre @8.31_0 (active)
  perl5 @5.12.4_0+perl5_12 (active)
  perl5.12 @5.12.4_1 (active)
  pkgconfig @0.27.1_2 (active)
  py27-cairo @1.10.0_1+x11 (active)
  py27-cheetah @2.4.4_1 (active)
  py27-distribute @0.6.34_0 (active)
  py27-gobject @2.28.6_0 (active)
  py27-lxml @2.3.2_0 (active)
  py27-nose @1.2.1_1 (active)
  py27-numpy @1.6.2_1 (active)
  py27-pygtk @2.24.0_0+x11 (active)
  py27-sip @4.14.2_0 (active)
  python27 @2.7.3_1 (active)
  python_select @0.3_2 (active)
  qt4-mac @4.8.4_2 (active)
  readline @6.2.000_0 (active)
  shared-mime-info @1.0_0 (active)
  sox @14.4.0_2 (active)
  sqlite3 @3.7.15.1_0 (active)
  tiff @3.9.7_0 (active)
  twolame @0.3.13_1 (active)
  urw-fonts @1.0.7pre44_0 (active)
  wavpack @4.60.1_0 (active)
  webp @0.2.1_0 (active)
  wget @1.14_1+ssl (active)
  Xft2 @2.3.1_0 (active)
  xorg-bigreqsproto @1.1.2_0 (active)
  xorg-compositeproto @0.4.2_0 (active)
  xorg-damageproto @1.2.1_0 (active)
  xorg-fixesproto @5.0_0 (active)
  xorg-inputproto @2.2.99.1_0 (active)
  xorg-kbproto @1.0.6_0 (active)
  xorg-libice @1.0.8_0 (active)
  xorg-libpthread-stubs @0.3_0 (active)
  xorg-libsm @1.2.1_0 (active)
  xorg-libX11 @1.5.0_0 (active)
  xorg-libXau @1.0.7_0 (active)
  xorg-libxcb @1.9_0+python27 (active)
  xorg-libXcomposite @0.4.3_0 (active)
  xorg-libXcursor @1.1.13_0 (active)
  xorg-libXdamage @1.1.3_0 (active)
  xorg-libXdmcp @1.1.1_0 (active)
  xorg-libXext @1.3.1_0 (active)
  xorg-libXfixes @5.0_0 (active)
  xorg-libXi @1.6.1_0 (active)
  xorg-libXinerama @1.1.2_0 (active)
  xorg-libXrandr @1.4.0_0 (active)
  xorg-libXt @1.1.3_0 (active)
  xorg-randrproto @1.4.0_0 (active)
  xorg-renderproto @0.11.1_0 (active)
  xorg-util-macros @1.17_0 (active)
  xorg-xcb-proto @1.8_0+python27 (active)
  xorg-xcb-util @0.3.9_0 (active)
  xorg-xcmiscproto @1.2.2_0 (active)
  xorg-xextproto @7.2.1_0 (active)
  xorg-xf86bigfontproto @1.2.0_0 (active)
  xorg-xineramaproto @1.2.1_0 (active)
  xorg-xproto @7.0.23_0 (active)
  xorg-xtrans @1.2.7_0 (active)
  xrender @0.9.7_0 (active)
  xz @5.0.4_0 (active)
  zlib @1.2.7_0 (active)
sh-3.2# 

remaining stuff in a moment

[michaelld (Michael Dickens)]

That all looks normal. I even switched my MacPorts install to be what you have, and configuring py27-pyqt4 works for me. I am running 10.8, but that's the only real difference. So, I'll await your reply about the rest of the stuff; but, I'm beginning to wonder if it's maybe your OS install that's not quite right.

[cgcgcg@…]

sh-3.2# cd `port dir py27-pyqt4`/work/PyQt-mac-gpl-4.9.6
sh-3.2# gdb qtdirs.app/Contents/MacOS/qtdirs
GNU gdb 6.3.50-20050815 (Apple version gdb-1822) (Sun Aug  5 03:00:42 UTC 2012)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries .... done

(gdb) r
Starting program: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_python_py-pyqt4/py27-pyqt4/work/PyQt-mac-gpl-4.9.6/qtdirs.app/Contents/MacOS/qtdirs 
Reading symbols for shared libraries +++.................................................................................................... done

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000000
0x0000000000000000 in ?? ()
(gdb) bt
#0  0x0000000000000000 in ?? ()
#1  0x00000001001553f7 in QIconvCodec::createIconv_t ()
#2  0x0000000100156171 in QIconvCodec::convertToUnicode ()
#3  0x000000010007559d in QString::fromLocal8Bit ()
#4  0x000000010000b365 in QSystemLocale::fallbackLocale ()
#5  0x000000010004cc5b in QLocalePrivate::updateSystemPrivate ()
#6  0x00000001000532ab in QLocale::QLocale ()
#7  0x00000001000c75ca in QResourceFileEnginePrivate::QResourceFileEnginePrivate ()
#8  0x00000001000c6000 in QResourceFileEngine::QResourceFileEngine ()
#9  0x00000001000f0038 in _q_resolveEntryAndCreateLegacyEngine_recursive ()
#10 0x00000001000f04a9 in QFileSystemEngine::resolveEntryAndCreateLegacyEngine ()
#11 0x00000001000b262b in QFileInfoPrivate::QFileInfoPrivate ()
#12 0x00000001000b11ff in QFileInfo::QFileInfo ()
#13 0x00000001000ad234 in QFile::exists ()
#14 0x0000000100020add in QLibraryInfoPrivate::findConfiguration ()
#15 0x0000000100020ea9 in QLibrarySettings::QLibrarySettings ()
#16 0x0000000100020f2b in qt_library_settings ()
#17 0x000000010002100b in QLibraryInfo::location ()
#18 0x000000010011f4c1 in QCoreApplication::libraryPaths ()
#19 0x0000000100120b4a in QCoreApplication::init ()
#20 0x0000000100120bcf in QCoreApplication::QCoreApplication ()
#21 0x0000000100001d40 in main (argc=1, argv=0x7fff5fbff9e8) at qtdirs.cpp:16
(gdb) 

[cgcgcg@…]

i have also some lines in console like:

11.01.13 21:15:12,073 mds: (Error) Backup: doBackupIndexFile could not stat backup location /.MobileBackups/Computer/2013-01-11-211209/Volume/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/python/py-pyqt4/work /.MobileBackups/Computer/2013-01-11-211209/Volume/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/python/py-pyqt4/work. Error 2 with uid 0

[michaelld (Michael Dickens)]

Well darn. The gdb output isn't any more helpful than the crash log. Seems like Qt is having issues creating an iconv_t.

Interesting regarding the backup error. I have no idea what it means. I somehow doubt it is relevant; but, maybe so.

I'll think about this issue over the weekend and hopefully come up with something else to try. We've tried all of the "usual tricks" and then some!

[cgcgcg@…]

ok, maybe i will buy a external disk and do some cloning / reinstalling lion and try again.
but for now this is my machine for every day work and this has priority.
thank you very much for deep bug hunting. if i have news i will report.

(bow)

[michaelld (Michael Dickens)]

Here's another one to try:

cd /usr
sudo mv local local_tmp
sudo port clean py27-pyqt4
sudo port -f uninstall qt4-mac
sudo port install qt4-mac
sudo port install py27-pyqt4

and see if that works. Then, to move everything back after this:

cd /usr
sudo mv local_tmp local

Or, if you don't use the stuff in /usr/local, you can just leave it as moved. I'm pretty sure MacPorts provides ports for the projects that are installed in /usr/local, if you want to use them.

[michaelld (Michael Dickens)]

I will also ask around to other MacPorts developers to see if one with a 10.7 box can replicate your issue. Thanks for your patience and persistence!

[cgcgcg@…]

did

cd /usr
sudo mv local local_tmp

restart

sudo port clean py27-pyqt4
sudo port -f uninstall qt4-mac
sudo port install qt4-mac
sudo port install py27-pyqt4

Error: org.macports.configure for port py27-pyqt4 returned: configure failure: command execution failed

main-log attached

[cgcgcg@…]

did another ticket for the running copy on mountain lion #37619, but that is maybe a simple question

[michaelld (Michael Dickens)]

From what I've heard back from other developers, none have issues with py27-pyqt4 on 10.7. So, somehow your install is "special" :)

When you do "sudo port install qt4-mac", does it install from binary or source?

[cgcgcg@…]

i would say from source, because it says "building" wich takes some time with lot of fan activity.
i think this happend for every time i reinstalled qt4-mac.
it looks like some sources returned 404, so it is cycling through until it finds one.

sh-3.2# sudo port install qt4-mac
--->  Computing dependencies for qt4-mac
--->  Fetching archive for qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_2.darwin_11.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_2.darwin_11.x86_64.tbz2 from http://lil.fr.packages.macports.org/qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_2.darwin_11.x86_64.tbz2 from http://packages.macports.org/qt4-mac
--->  Attempting to fetch qt4-mac-4.8.4_2.darwin_11.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/qt4-mac
--->  Fetching distfiles for qt4-mac
--->  Verifying checksum(s) for qt4-mac
--->  Extracting qt4-mac
--->  Applying patches to qt4-mac
--->  Configuring qt4-mac
--->  Building qt4-mac
--->  Staging qt4-mac into destroot
--->  Installing qt4-mac @4.8.4_2
--->  Activating qt4-mac @4.8.4_2
--->  Cleaning qt4-mac
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

[michaelld (Michael Dickens)]

Yes, that's from source; which is good, I think. I will continue to think about other things you could try to either debug or fix this issue. I'm at a loss for other suggestions just right now.

How badly do you need to items in /usr/local (and, the few extra in /Library/Frameworks)? Can you do a full backup of your boot drive, wipe it clean, reinstall 10.7 from scratch, restore your login and its data (only; nothing else into /Library/Frameworks or /usr/local), then try again with MacPorts and PyQt4? I know this would take a significant effort, and this being your primary work computer you likely don't want to have to do this. If not, is there any way you could grant me remote access to poke around and see what I can figure out? I promise to keep my activities to this ticket's issues, but I do not promise that I can fix the issue even with remote access; I just think of it as an alternative to this async back and forth.

[cgcgcg@…]

i got a feeling this has to do with parallels desktop, which is crashing now over QtCorePrl
reinstalling and reimporting all data maybe i will do later because "never change a running system" and i need my configuration incl. parallels
if there is a relation between this crash and qt4-mac, restoring parallels has priority, sorry
On mac mini i'm now running successfully ports of gnuradio, rtl-sdr and "maked" gr-osmosdr.
Thank you very much!

[michaelld (Michael Dickens)]

Well, I'm glad that you have 1 computer up and working.

From that last crash log, I can see that parallels uses its own (internal) version of Qt4 (4.7), but it crashes in a fashion similar to the MacPorts' installed version (4.8). I guess this makes me feel better ;) So, there's a common theme between the 2 independent installs.

Have you ever in the past had success with PyQt4 (via MacPorts or otherwise)? How about Parallels? Or, did these stop working suddenly (recently)?

What does "env" return from in your shell?

[cgcgcg@…]

maybe i was a bit noobish. I think it was at the first try to install gnuradio at 30.12.2012. It depended qt lib. So i installed a package from somewhere. Gnuradio installation still failed and some programs began to crash. I tried to uninstall qt lib which did not fixed the crashes. I think i followed this site: ​http://qt-project.org/forums/viewthread/20971/. At last, at January 2 or 3 i restored from a time machine backup, back to december 29. It seem that restoring from time machine did not fix the problem. But now i can't see what package i actually had in downloads or on which websites i was in that time. For me, this is a noobish bug for itself. (giggle)

christoph$ env
TERM_PROGRAM=Apple_Terminal
TERM=xterm-256color
SHELL=/bin/bash
TMPDIR=/var/folders/ln/3v_5w6xj4ks2fg9y51wgvzcw0000gn/T/
Apple_PubSub_Socket_Render=/tmp/launch-IijB9C/Render
TERM_PROGRAM_VERSION=303.2
TERM_SESSION_ID=B4C2C208-75A8-47B5-8608-18DA98469A96
USER=christoph
COMMAND_MODE=unix2003
SSH_AUTH_SOCK=/tmp/launch-JusHQk/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:0:3
Apple_Ubiquity_Message=/tmp/launch-yrXaAg/Apple_Ubiquity_Message
PATH=/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/opt/local/bin:/opt/local/sbin:/Applications/MAMP/Library/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/MacGPG2/bin
PWD=/Users/christoph
LANG=de_DE.UTF-8
SHLVL=1
HOME=/Users/christoph
LOGNAME=christoph
DISPLAY=/tmp/launch-ME9xcD/org.x:0
SECURITYSESSIONID=186a4
_=/usr/bin/env

[michaelld (Michael Dickens)]

The "env" looks fine, except maybe the MAMP part in PATH -- but it probably doesn't make any difference.

I'm guessing that whatever Qt you installed before has some residual stuff around somewhere, and that's what's causing this issue. The only full Qt binary distros I know of are provided by MacPorts, Fink, Homebrew, and the Qt project itself; none of these should cause the type of crash you're experiencing in and of themselves. And, your listing of various directories well above shows that there isn't much left around in the usual places. If you installed from the Qt project's binary, there is generally still stuff around in "/Developer/Applications/Qt" (and, other /Developer locations and /usr/local/Qt*). So, quite the mystery. If you reinstall Parallels, after fully deleting the current .app, does it still crash in the same way? That would point to something external to Parallels as the cause.

[cgcgcg@…]

I found a file "PyQtX+_py273_q482_pyqt494.pkg.mpkg" in my download folder from 23.12.2012. Trying to install failed, leaving my computer in unknown state. Probably this also happend in december and my time machine restored to already half installed PyQtX+_py273_q482_pyqt494.pkg.mpkg. Searching for ""PyQtX+_py273_q482_pyqt494.pkg.mpkg"" brings me to ​http://sourceforge.net/projects/pyqtx/ . I attached install.log.

[michaelld (Michael Dickens)]

That installer seems to install a bunch of stuff: Python 2.7.3, Qt 4.6.4(!), and if it worked then PyQt4 4.9.4. The first 2 are installed, while the installer bombed out before the latter. I could easily see how this binary install might mess up a new/fresh install from source.

Is there a script "/Developer/Tools/uninstall-qt.py"? That should remove the Qt stuff. That said, I have Qt 4.8.3 (from the Qt project's binaries) installed to make sure that qt4-mac builds against it without using its stuff; or, at least that's the idea. Maybe I'll go get 4.6.4, install it, and see if py27-PyQt4 still works.

To remove the Python stuff, it looks like you could do:

cd /Library/Frameworks
sudo rm -rf Python.framework

and, since the PyQt4 stuff wasn't installed this time I'm not sure how to remove it if it was installed before.

[cgcgcg@…]

mailed to the owner of that package for suggestions how to remove it completely

[cgcgcg@…]

ok, i'm running in cycles. As my new installed mac mini get more and more configured there is no need anymore to stay with Lion. I'm think about ending this debugging and doing a fresh install with 10.8. Trying too much with pacifist and pkgutil would be too dangerous and less informative. I hope it is ok leaving this ticket invalid, but i think my settings are too mixed up and im not able to fix it manually. Thank you very much for your extensive support!

lg cg

[michaelld (Michael Dickens)]

No problems if you want to declare this ticket as "invalid". I think we found the issue -- the precompiled stuff that was partially installed and partially removed -- and luckily this has never been reported as a ticket issue before so your install is "special" somehow. We just never figured out how to work around the still-installed crud; not a bit issue if we never do figure this out. Just pop back here with the formal word that you're moving to 10.8 and I'll close this ticket.

[michaelld (Michael Dickens)]

You're welcome for all the work; I hope you resolved the issue and have PyQt4 working on your setup again. I'm going to go ahead and close this ticket.

[cgcgcg@…]

ok, sorry for delay. I had to work on. The last i did was deinstalleing the stuck package in PyQtX+_py273_q482_pyqt494.pkg.mpkg with the help of pacifist. Then reinstalled PyQtX+_py273_q482_pyqt494.pkg.mpkg again with no errors, leaving my mac again pointing to wrong python and qt. Finding everything with pacifist and manually removing all of PyQtX+_py273_q482_pyqt494.pkg.mpkg seem too dangerous for me. I prefer moving to a fresh mountain lion and reimporting my data. But if you really like to see whats going on and fix the bindings to macport side i can clone my system and mount it on another computer for remote debugging as you mentioned in comment 45. If so, what do you think is the best way to do this?

[michaelld (Michael Dickens)]

I think I can recreate the issue on my computer (after backing it up carefully). So, thanks for the offer, but please don't bother with the clone and remote debugging on my behalf especially since it'll take you quite a bit of time to do that. BTW> My preferred way of this sort of backup is ​CarbonCopyCloner.

[cgcgcg@…]

great, thank you. Is it difficult to fix? Allways have fun learning something like that. I cloned my disk already with Superduper, ready to boot it on my second mac while being able to do my work.

[michaelld (Michael Dickens)]

I haven't backed up my computer for this purpose yet (meaning, being really thorough; creating a full copy fir CCC or SuperDuper where if all else fails I can get back to where I started) -- so I'm not sure how difficult the fix will be. I'm guessing it's a matter on your (the user's) side of removing the correct files, and on my (MacPorts) side of explicitly specifying the correct settings (e.g., Python to use; #include directory to use; whatever). I'm in no rush to get this done, but do let me know if your upgraded system has the same issue and I'll push this up on my queue.

[cgcgcg@…]

I'm playing around with gnuradio on the fresh installed mountain lion mac mini, trying tutorials, reading 433mhz temp sensors ... It is a whole new world for me and i getting deeper and deeper into python, perl and portfiles. I'm sure a fresh install on my working machine will do it also without problems. But im not in rush with new install until i know all of my working environment is running fine under ML. IF something macport related is not working as expected i will let you know. Until then i thank you very much for you're good work and great support. It is much fun for me.

best cg

[michaelld (Michael Dickens)]

Good to hear and all sounds good. You're welcome! Good luck with your GR work and learning the various languages needed therein :) - MLD