MacPorts 2.0.4 and recommendation for Lion Xcode version

Tabitha McNerney tabithamc at gmail.com
Sun Mar 18 19:11:55 PDT 2012


On Sat, Mar 17, 2012 at 7:16 PM, Ryan Schmidt <ryandesign at macports.org>wrote:

>
> On Mar 17, 2012, at 04:56, Tabitha McNerney wrote:
>
> > My boss asked me to install MacPorts on a new iMac that arrived to our
> office last week, and it shipped with Mac OS X Lion 10.7.3 (so we probably
> can't run Snow Leopard on it). I've downloaded MacPorts 2.0.4 but I'm
> wondering if I should install it using a slightly older version of Xcode
> for Lion (like 4.2.1) or if its generally ok and recommended to use
> MacPorts 2.0.4 with Xcode 4.3.1 (which is the current version offered in
> the App Store)? I ask because I seem to recall not too long ago there were
> some problems with getting MacPorts to work well with Xcode 4.3.x.
>
> I guess go ahead and use Xcode 4.3.1; MacPorts was largely fixed to work
> with Xcode 4.3.x in version 2.0.4. You'll probably run into some individual
> ports that don't work with this version of Xcode yet. As you would anytime
> any port fails to build, please file bug reports in these situations so
> that we can fix them.
>


Thank you Ryan for the insight and suggestions. So far so good, but I have
quite a few more Mac Ports in my extensive list to build. I noticed the
warning when initially configuring MacPorts 2.0.4 which stated:

Warning: xcodebuild exists but failed to execute
> Warning: Xcode appears to be installed but xcodebuild is unusable; some
> ports will likely fail to build.
> Warning: You may need to run `sudo xcode-select -switch
> /Applications/Xcode.app`
>

I was required to run `sudo xcode-select -switch /Applications/Xcode.app`
when trying to install the zlib port, but once I ran this, it worked fine.
So, I don't really know if this qualifies as a bug. Also, I'm not sure if
this would qualify as a bug -- when building the gmp port, I got this
Warning in the output:

Warning: No processor dependent assembly code being used. gmp might be
> slower.
>

But then the process continued successfully:

--->  Building gmp
> --->  Staging gmp into destroot
> --->  Installing gmp @5.0.4_0
> --->  Activating gmp @5.0.4_0
> --->  Cleaning gmp
>

I will definitely file bug reports for situations where a port fails to
build. Should I also file bug reports for warning messages like the one for
gmp?

Thank you,

-Tabitha
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macports-users/attachments/20120318/f4d9967c/attachment.html>


More information about the macports-users mailing list