/Developer symlink with xcode 4.3

Dan Ports dports at macports.org
Tue Feb 28 15:10:21 PST 2012


On Tue, Feb 28, 2012 at 11:26:48PM +0100, Benoit T wrote:
> Why again is it that one may have to symlink
> /Applications/Xcode.app/Contents/Developer to /Developer ?

You shouldn't ever have to do this.

> I had to do that in order to build py27-tkinter, a trivial package that
> does not have the string "/Developer" hard-coded anywhere in its work
> files nor portfile

The problem here is that the python27 port records the path to the
compiler that was used to build it, and uses that compiler to build
modules like py27-tkinter. In your case, that's the compiler in
/Developer.

You can fix this by rebuilding the python27 port, e.g. with
  port -n upgrade --force python27

Other ports that do the same thing (that I know of) include the other
python versions, perl5.x, apr, and postgresql.

We should either
 1) have the perl and python portgroups check that the compiler hardcoded
    into the interpreter is still available, and tell the user to
    rebuild as necessary
 2) make perl/python/etc modules build using ${configure.compiler}
    instead of the compiler used by the interpreter.

I'm inclined to do (1) at least as a temporary measure. (2) may be a
better fix but it's not clear to me that it's OK to switch the compiler
like that, and it would definitely call for some testing first.

Dan

-- 
Dan R. K. Ports              MIT CSAIL                http://drkp.net/


More information about the macports-dev mailing list