macports broken under Mountain Lion and Xcode 4.4?
msavory1 at nzbox.com
Fri Feb 17 19:55:29 PST 2012
Given that MacPorts is a purely volunteer group and that Apple gives them absolutely no warning about impending upgrades, and the fact that those of us with Developer accounts can't speak publicly about out findings, please relax, go back to your Time Machine backups (if necessary) and give people a chance to catch up.
Not that I am saying too much, but fixing the current Xcode 4.3 issues will help hugely to make the Mountain Lion upgrade pretty much a "bin there, done that" event.
(p.s. ML may run perfectly in Parallels Desktop (the tools and shared folders even), if you want to play without destroying your main system)
On Feb 17, 2012, at 7:32 PM, Scott Webster wrote:
> I'm sure people are generally going to be interested in information
> about Mountain Lion and Macports, but with Xcode 4.3 just out things
> are a little overloaded at the moment!
> On Fri, Feb 17, 2012 at 9:54 AM, Artemio Gonzalez Lopez
> <artemiog at mac.com> wrote:
>> Yesterday I installed Mountain Lion and Xcode 4.4 (including the Command Line Tools") in my MacBook Pro 15" (2011). While I succeeded in compling MacPorts from source (after completely erasing the previous installation), when I try to install any port via "sudo port -d install foo" I get the following error at the configure phase:
>> checking for gcc... /Applications/Xcode.app/Contents/Developer/usr/bin/clang
>> checking for C compiler default output file name...
>> configure: error: C compiler cannot create executables
>> See `config.log' for more details.
>> configure: error: ./configure failed for lib
>> shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gperf/gperf/work/gperf-3.0.4" && ./configure --prefix=/opt/local --infodir=/opt/local/share/info " returned error 1
>> There is obviously some problem in properly detecting the path to the C compiler, since clang it's not in /Applications/Xcode.app/Contents/Developer/usr/bin/ but in /usr/bin. Could anybody suggest a fix to this?
>> Thanks in advance,
>> Artemio Gonzalez Lopez
>> artemiog at me.com
>> macports-users mailing list
>> macports-users at lists.macosforge.org
> macports-users mailing list
> macports-users at lists.macosforge.org
More information about the macports-users