Compiler toolchain

[Clemens Lang]

Hi,

On Tue, Apr 03, 2012 at 09:05:03PM +0200, Michael Feiri wrote:
> A while ago I've put some effort into packaging several of Apple's
> open source developer components as macports ports. It turned out that
> just a handful of ports are necessary to have a self-contained
> compiler toolchain. Such a toolchain could allow us to be
> self-contained in the sense that for most of our needs we don't need
> to rely on Xcode any more. Here is a list of relevant ports:

On Mon, Apr 09, 2012 at 01:23:34PM -0700, Dan Ports wrote:
> This sounds like a pretty serious problem now that we have binary
> packages. It was already an issue before, because it meant that
> python/perl/etc needed to be rebuilt if the compiler moved. But now
> it's worse, because the compiler path that's getting hardcoded into
> the Python binary is the one used on our buildbot. (It doesn't help
> that the buildbot is using an older version of Xcode, but this would
> still be an issue if it were running the latest version).

I see a potential synergetic effect here... if we were using our own
toolchain this problem wouldn't occur.

-- 
Clemens Lang