In message <201505190123.t4j1n4qc029...@elvis.arl.psu.edu>, John D Groenveld
writes:
>Does anyone have a build recipe for LLVM/clang on OmniOS?
LLVM depends on CMake and Python-2.7.9.
Both build easily with stock gcc-4.8.1.
John
groenv...@acm.org
___
O
ISTR there being an old pull request in omnios-build for it. I can't just take
something like that in, but it may serve your needs.
Dan
Sent from my iPhone (typos, autocorrect, and all)
> On May 18, 2015, at 9:23 PM, John D Groenveld
> wrote:
>
> In message
> ,
> Tim Rice writes:
>> Any re
In message ,
Tim Rice writes:
>Any reason not to consider CLANG instead of GCC?
Does anyone have a build recipe for LLVM/clang on OmniOS?
I'm about to try that path to build Google's V8.
John
groenv...@acm.org
___
OmniOS-discuss mailing list
OmniOS-dis
> On May 18, 2015, at 6:31 PM, Tim Rice wrote:
>>
>> My question to you all is this: To which gcc version should we jump? I see
>> two viable candidates:
>
> Any reason not to consider CLANG instead of GCC?
Completely new beast and potential for least-surprise. I can imagine
CLANG/LLVM sh
On Mon, 18 May 2015, Dan McDonald wrote:
> Now this isn't a gcc update for illumos/illumos-omnios... that way is full of
> pain, and I'll wait for now.
>
> OTOH, we've transitioned gcc before going into r151008 with 4.8.1.
>
> My question to you all is this: To which gcc version should we jump
On Mon, May 18, 2015 at 4:56 PM, Volker A. Brandt wrote:
> Naïvely, shouldn't the newer be better? Less work during the the next
> version jump...
The very first thing on the 5-series changes list
(https://gcc.gnu.org/gcc-5/changes.html):
* The default mode for C is now -std=gnu11 instead of -
On Mon, May 18, 2015 at 4:38 PM, Dan McDonald wrote:
> My question to you all is this: To which gcc version should we jump? I see
> two viable candidates:
>
> - gcc 4.9.2 (last updated October 2014)
>
> or
>
> - gcc 5.1 (last updated April 2015)
>
> The current gcc "development"
> My question to you all is this: To which gcc version should we jump?
> I see two viable candidates:
>
> - gcc 4.9.2 (last updated October 2014)
>
> or
>
> - gcc 5.1 (last updated April 2015)
Naïvely, shouldn't the newer be better? Less work during the the next
version jump...
R
Now this isn't a gcc update for illumos/illumos-omnios... that way is full of
pain, and I'll wait for now.
OTOH, we've transitioned gcc before going into r151008 with 4.8.1.
My question to you all is this: To which gcc version should we jump? I see
two viable candidates:
- gcc 4.9.2
