Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 04 Jun 2010 21:28:40 +0300
From:      =?utf-8?B?QW5kcml1cyBNb3JrxatuYXM=?= <hinokind@gmail.com>
To:        "Doug Barton" <dougb@freebsd.org>
Cc:        Roman Divacky <rdivacky@freebsd.org>, current@freebsd.org
Subject:   Re: [INFO]: import of clang/LLVM to happen on June 9th
Message-ID:  <op.vdsf92ux43o42p@klevas>
In-Reply-To: <4C093D60.1010008@FreeBSD.org>
References:  <20100604152605.GA80277@freebsd.org> <4C0930E3.3030301@FreeBSD.org> <op.vdsd81uu43o42p@klevas> <4C093D60.1010008@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 04 Jun 2010 20:52:32 +0300, Doug Barton <dougb@freebsd.org> wrote:
> Sorry I wasn't clear. I'm not talking about compiling ports with clang
> (which I also look forward to someday) I'm talking about installing a
> version of gcc from ports and using that to compile all the other ports.

I'm even more confused now. What does that have to do with clang import?

And I guess I wasn't too clear myself. I was talking about "setting ports
compiler to whatever you want", not "compiling ports with clang". I guess
PortsAndClang page would only explain how to change the compiler to clang,
but there's already a tutorial about changing ports compiler to newer
version of gcc[1].

So what am I missing here?

[1] http://www.freebsd.org/doc/en_US.ISO8859-1/articles/custom-gcc/configuring-ports-gcc.html

-- 
Andrius



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.vdsf92ux43o42p>