Yet another macports/qt/mac nightmare...
Alec Jacobson
May 06, 2011
Today I wasted countless hours recompiling all sorts of junk on my computer. The culprits once again are macports, Qt and Apple's 32-bit/64-bit androgyny.
I recently upgraded from mac os x 10.5 (where 32-bits is default) to mac os x 10.6 (where 64-bits is default). Macports naturally pretends to work just fine after I make the switch. Low and behold it's little house on the sand is about to wash away. Today I wanted to upgrade to the latest version of pdflatex. I tried to do so using macports. No go. Eventually I found the "migration" guide for "migrating" you macports after you upgrade from mac os x 10.5 to mac os x 10.6. Their idea of "migration" is uninstalling and reinstalling everything! All of my 300 some ports needed to be recompiled. Their instructions by the way did not work as it didn't account for external dependencies still hanging around in i386, 32-bit mode.
I've finally reinstalled pdflatex. But now my Qt installation doesn't work.
I tried:
sudo port install qt4-mac
and about a year later everything seemed to have worked fine. Kudos to macports for having the bright idea to restrain from distributing precompiled binaries. I'm learning patience!
But everything did not work fine. I re-qmake-ed my current project into an xcode project which went fine, but when I tried to build my project in xcode I got the following mysterious error:
pbxcp: warning: couldn't strip: /absolute/path/to/my/app: No such file or directory
Searching around the only ideas I found were to delete the build directory, clean and rebuild which did not work.
Solution:
sudo port deactivate qt4-mac
Install Qt SDK directly from Qt site (hours faster than macports by the way).