On Thu, Jul 12, 2012 at 3:34 AM, Michael Goffioul
<address@hidden> wrote:
> On Tue, Jul 10, 2012 at 2:36 PM, Jordi Gutiérrez Hermoso
> <
address@hidden> wrote:
>>
>> Hi, guys.
>>
>> The JIT branch needs a bit more love and code review:
>>
>>
http://inversethought.com/hg/octave-max/
>>
>> Please clone it and attempt to build it, especially on non-GNU
>> systems.
>
>
> trying to work around:
> 1) llvm-config is not built (need to hack the cmake files to make it built)
Using llvm-config seemed like the easiest way to locate llvm. I didn't
know that it was not available on all systems. Is there some way I can
change the configure script to make this easier?
Apparently, the problem only occurs on non-MSYS/non-CYGWIN platforms. This probably reduces the number of affected people to 1 (me). As I'm using MSYS as compilation environment, I have "sed" available anyway (this is the reason llvm-config is not compiled on pure Win32 platform), so I hacked my llvm to force compilation of llvm-config.
> 2) configure.ac unconditionally uses "-isystem" compiler flag (I can
> probably hack my compiler wrapper to support it, but what's the reason for
> doing that?)
The issue is that including the llvm headers caused lots of warnings
in gcc. I got around this by using -isystem. Is there a better way to
do this? At the very least I could check to see if -isystem is
supported before using it.
Maybe these warnings are "normal", or maybe they should be reported. Anyway, did you check whether "llvm-config --cflags" contain some compilation flags that would make those warnings to disappear? For instance under MSVC, the llvm compilation flags contain a bunch of warning disabling.
In the meantime, I've hacked my MSVC wrapper to support -isystem, so again this is not a problem anymore for me. I suppose you could check whether the -isystem flag is supported and use "-I`llvm-config --includedir`" if it's not.
Michael.