On Sep 6, 2014, at 5:32 AM, Dimitry Andric wrote:
> On 06 Sep 2014, at 05:16, Warner Losh wrote:
>>
>> On Sep 5, 2014, at 8:21 PM, Garrett Cooper wrote:
>>>
>>> One of the questions that came up from a co-worker is "why do I
>>> need to build clang in buildworld if I already installed it fr
On Sep 6, 2014, at 5:28 AM, David Chisnall wrote:
> On 6 Sep 2014, at 06:47, Garrett Cooper wrote:
>
>> Makes sense. I'll do some poking around and see if things could potentially
>> be optimized with the clang build. On beefy machines it's not a big deal,
>> but as we know on machines witho
On 6 Sep 2014, at 06:47, Garrett Cooper wrote:
> Makes sense. I'll do some poking around and see if things could potentially
> be optimized with the clang build. On beefy machines it's not a big deal, but
> as we know on machines without a ton of memory or SSDs, it can become
> painful, as exp
On 06 Sep 2014, at 05:16, Warner Losh wrote:
>
> On Sep 5, 2014, at 8:21 PM, Garrett Cooper wrote:
>>
>> One of the questions that came up from a co-worker is "why do I
>> need to build clang in buildworld if I already installed it from
>> ports"? I could see some valid reasons for doing this
> tl;dr: NO.
Makes sense. I'll do some poking around and see if things could potentially be
optimized with the clang build. On beefy machines it's not a big deal, but as
we know on machines without a ton of memory or SSDs, it can become painful, as
expected.
Thanks :)!
-Garrett
__
On Sep 5, 2014, at 8:21 PM, Garrett Cooper wrote:
> Hi all,
>One of the questions that came up from a co-worker is "why do I
> need to build clang in buildworld if I already installed it from
> ports"? I could see some valid reasons for doing this (one needs a
> cross-compiler, one might nee
Hi all,
One of the questions that came up from a co-worker is "why do I
need to build clang in buildworld if I already installed it from
ports"? I could see some valid reasons for doing this (one needs a
cross-compiler, one might need specific options that might not be set
in the ports version)