I tried upgrading outdated ports, and got the above error message. (It's always
worked before.) Anyway, I did the xcode-select thing, and still, no dice.
Anyone else experience this?
(Mac OS X 10.7.4, Xcode 4.3.2). Here's the output:
Sat May 12 08:29:21 -- Me ~ :: sudo port upgrade outdated;
On May 12, 2012, at 09:33, René Fournier wrote:
I tried upgrading outdated ports, and got the above error message. (It's
always worked before.) Anyway, I did the xcode-select thing, and still, no
dice. Anyone else experience this?
Lots of people, if you look in the mailing list archives.
On 2012-05-12, at 11:58 AM, Ryan Schmidt wrote:
On May 12, 2012, at 09:33, René Fournier wrote:
I tried upgrading outdated ports, and got the above error message. (It's
always worked before.) Anyway, I did the xcode-select thing, and still, no
dice. Anyone else experience this?
Xcode 4.3.2
Build version 4E2002
And what's `xcode-select -print-path` show?
My guess is you need to use
/Applications/Xcode.app/Contents/Developer
rather than
/Applications/Xcode.app
Also, just checking: xcode-select -version
xcode-select version 2307
smime.p7s
Description: S/MIME
On Sat, May 12, 2012 at 12:27 PM, René Fournier m...@renefournier.com wrote:
This problem is affecting a production machine, so I really need to solve it
quickly. I reinstalled Xcode from the App Store, installed the command line
tools... What else can I do?
You made critical, untested
On 2012-5-13 05:48 , Jack Howarth wrote:
Is anyone else finding that a clean install of MacPorts 2.1.0-rc2 from
the source tarball on 10.7.4 with Xcode 4.3.2 results in the installed
MacPorts building packages with llvm-gcc rather than clang? Is there a quick
fix to hack port to properly
Thanks :)
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
