MacPorts requires Xcode 4.1 under Lion

[peter@…]

Xcode 3.2.5 is allowed by Apple in Lion, and is required by some of us for development reasons.

MacPorts should not require Xcode 4.x for Lion.

[mf2k (Frank Schima)]

Just curious, why not Xcode 3.2.6 which is the last of the 3.2.x series?

[jmroot (Joshua Root)]

I was under the impression that Xcode 3.2.x refuses to install on Lion. I know from experience that the Lion installer removes the "UNIX Development" bits, which MacPorts needs. Does it not work to use Xcode 3.2 in /Developer-old while having Xcode 4.1 in /Developer and its UNIX Development and System Tools in /usr?

[peter@…]

Replying to macsforever2000@…:

Just curious, why not Xcode 3.2.6 which is the last of the 3.2.x series?

No particular reason, its just the one I had installed before upgrading to Lion.

[peter@…]

Replying to jmr@…:

I was under the impression that Xcode 3.2.x refuses to install on Lion. I know from experience that the Lion installer removes the "UNIX Development" bits, which MacPorts needs. Does it not work to use Xcode 3.2 in /Developer-old while having Xcode 4.1 in /Developer and its UNIX Development and System Tools in /usr?

No, this is incorrect. If you have Xcode 3.2.x installed, and upgrade to Lion, it is still there and works as normal. Also, you can install 3.2.x under Lion - certainly you can install 3.2.5 under Lion because I did this yesterday without issue, except that then MacPorts refused to work saying it requires 4.1 for some reason.

If there is a *really* good reason MacPorts requires 4.1, fair enough, it just means I can't use MacPorts. But I don't see why it would require 4.1.

[danielluke (Daniel J. Luke)]

At least one really good reason is that the more configurations we try to support, the harder it is.

If you wanted to volunteer to make sure everything works under Xcode 3.2.x (and fixed up everything that didn't), I'm sure we would include whatever changes were necessary.

If you want to just do it yourself, you can probably figure out how to get macports to build and install with a non-recommended version of Xcode, but you're not likely to get support from anyone else if you run into issues.

[peter@…]

Replying to dluke@…:

At least one really good reason is that the more configurations we try to support, the harder it is.

If you wanted to volunteer to make sure everything works under Xcode 3.2.x (and fixed up everything that didn't), I'm sure we would include whatever changes were necessary.

If you want to just do it yourself, you can probably figure out how to get macports to build and install with a non-recommended version of Xcode, but you're not likely to get support from anyone else if you run into issues.

Fair enough, sorry I wasted your time reporting it.

[afb@…]

You can install Xcode 2.5 on (Snow) Leopard too, for the same legacy reasons.

But the one in /usr and /Developer, should be the recommended native version.