[MacPorts] #26391: Bogues XCode too old message
MacPorts
noreply at macports.org
Wed May 25 20:08:06 PDT 2011
#26391: Bogues XCode too old message
--------------------------------+-------------------------------------------
Reporter: ralph@… | Owner: macports-tickets@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: base | Version: 1.9.1
Resolution: | Keywords:
Port: |
--------------------------------+-------------------------------------------
Comment(by arritjenof@…):
I'd like to add another observation.
As i wrote, i have two seperate OSX-installs, each on a seperate
partiotion. The main partition (hd) and a secondary partition (hds).
On {{{hd}}} the OS is fully up-to-date, and it has XCode 4.0.1 installed.
On {{{hds}}} an older version of 10.6 is installed, and XCode 3.2.6.
Perhaps noteworthy is the fact that I installed XCode 3.2.6 on the
secondary partition while being booted into the 'main' OS on {{{hd}}}
(that already had XCode 4.0.1 installed)
Anyway, i just did some digging, and found 3 versions of xcodebuild
present on my machine:
{{{
$ > which xcodebuild
/usr/bin/xcodebuild
$ > /usr/bin/xcodebuild -version
XcodeComponent versions: DevToolsCore-1809.0; DevToolsSupport-1806.0
BuildVersion: 10M2518
$ > /Developer/usr/bin/xcodebuild -version
Xcode 4.0
Build version 4A1006
$ > /Volumes/hds/Developer/usr/bin/xcodebuild -version
XcodeComponent versions: DevToolsCore-1809.0; DevToolsSupport-1806.0
BuildVersion: 10M2518
}}}
along the way, i also found the {{{xcode-select}}} tool
{{{
$ > man xcode-select
…
DESCRIPTION
xcode-select controls the location of the Xcode folder
which will be used by xcodebuild(1) and
other, related Xcode BSD tools. This allows you to easily
switch between using different versions
of the Xcode tools
…
}}}
{{{
$ > xcode-select -print-path
/Volumes/hds/Developer
}}}
appearantly, installing the older XCode version on the secondary
partition, also changed the default {{{xcode_folder_path}}}.
and it seems the {{{xcodebuild}}} binary in {{{/usr/bin/}}} is just stub,
invoking the {{{xcodebuild}}} tool in the appropriate
{{{xcode_folder_path}}}...(?)
setting the {{{xcode_folder_path}}} to the main {{{/Developer}}} directory
again, fixed the ports-problem for me.
{{{
$ > sudo xcode-select -switch /Developer
$ > xcodebuild -version
Xcode 4.0
Build version 4A1006
}}}
to test, you can also play around with this configuration by setting the
environment variable {{{DEVELOPER_DIR}}},
this overrides whatever xcode-switch would output. see {{{man xcode-
switch}}}
{{{
$ > xcode-select -print-path
/Volumes/hds/Developer
$ > xcodebuild -version
XcodeComponent versions: DevToolsCore-1809.0; DevToolsSupport-1806.0
BuildVersion: 10M2518
$ > export DEVELOPER_DIR=/Developer/
$ > xcodebuild -version
Xcode 4.0
Build version 4A1006
}}}
So, i'd like to appologize for creating the confusion caused by my own
mess.
Ofcourse this still doesn't explain why the output of {{{xcodebuild
-version}}} for XCode 3.2.6 is not accepted by mac ports, but i hope this
info will help resolve that problem too..
--
Ticket URL: <https://trac.macports.org/ticket/26391#comment:21>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list