[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: --jit-enable
From: |
Rik |
Subject: |
Re: --jit-enable |
Date: |
Mon, 10 Sep 2012 13:36:06 -0700 |
On 09/10/2012 12:50 PM, address@hidden wrote:
> Message: 7
> Date: Mon, 10 Sep 2012 21:34:17 +0200
> From: Philip Nienhuis <address@hidden>
> To: Max Brister <address@hidden>
> Cc: Philip Nienhuis <address@hidden>,
> address@hidden
> Subject: Re: LLVM not picked up - too old version?
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Max Brister wrote:
>> > On Mon, Sep 10, 2012 at 1:05 PM, Philip Nienhuis
>> > <address@hidden> wrote:
>>> >> What version of LLVM is needed these days?
>>> >>
>>> >> I have llvm 3.0; configure output at the end doesn't mention the llvm
>>> >> libs/flags/include but only says something like:
>>> >> "JIT compiler for loops: false"
>>> >>
>>> >> AFAICR a week or two weeks ago it did pick up the llvm stuff (that is, I
>>> >> saw
>>> >> the llvm libs/include/flags mentioned in configure's output).
>>> >>
>>> >> linux Mageia 2, gcc 4.6.3, Pentium M
>>> >>
>>> >> Philip
>> >
>> > LLVM 3.0 should still work, I haven't tested it recently though.
>> > Recently there was a change that requires "--enable-jit" in order for
>> > JIT to be enabled.
> Thanks, yes --enable-jit=yes did the trick.
> I must have missed that announcement somehow.
>
> BTW I now see messages (using sources updated two hours ago):
> "cc1plus: warning: /usr/bin/llvm-config: not a directory {enabled by
> default]"
> repeated twice after every compile step. Should I start worrying?
Yes. That is unlikely to work. We can wait until the end of the compile,
but I think I want to see your config.log file.
--Rik