Re: Updating MXE to llvm-3.1

[Michael Goffioul]

On Tue, Jul 16, 2013 at 1:22 PM, PhilipNienhuis <address@hidden> wrote:

John Donoghue-2 wrote
> From: Michael Goffioul [mailto:

> michael.goffioul@

> ]
> Sent: Tuesday, July 16, 2013 12:52 PM
> To: John D
> Cc: Octave Maintainers List
> Subject: Re: Updating MXE to llvm-3.1
>
>
>

> On Tue, Jul 16, 2013 at 12:17 PM, John D &lt;

> john.david.donoghue@

> &gt;

> wrote:
>
> ------------------------------
>
> Message: 2
> Date: Mon, 15 Jul 2013 21:07:48 -0400

> From: Michael Goffioul &lt;

> michael.goffioul@

> &gt;
> To: Stefan Mahr &lt;

> dac922@

> &gt;
> Cc: Octave Maintainers List &lt;

> octave-maintainers@

> &gt;

> Subject: Re: Re: Updating MXE to llvm-3.1
> Message-ID:

>         &lt;

> address@hidden

> &gt;

> Content-Type: text/plain; charset="iso-8859-1"
>
> On Mon, Jul 15, 2013 at 5:37 PM, Michael Goffioul <

> michael.goffioul@

>> wrote:
>
>> On Mon, Jul 15, 2013 at 11:45 AM, Stefan Mahr &lt;

> dac922@

> &gt; wrote:
>>
>>> Michael D. Godfrey wrote:
>>> > Have you been following the maintainers llvm/jit thread?  Octave
>>> > devel currently supports llvm 3.1.and 3.2.
>>>
>>> AFAIK it supports LLVM 3.0 and 3.1. There's a patch for 3.2 in bug
>>> tracker, but it's not applied yet.
>>>
>>>
>>>
>>> Michael Goffioul wrote:
>>> > If it breaks horribly for everyone, we can consider downgrading,
>>> > but if
>>> not, it makes my life easier.
>>>
>>> [build]    llvm
>>>
>>> Failed to build package llvm!
>>> ------------------------------------------------------------
>>>   llvm-build: error: invalid target to enable: '' (not in project)
>>> -- Configuring incomplete, errors occurred!
>>>
>>
>> It seems the ';' in -DLLVM_TARGETS_TO_BUILD="X86;" is causing the
>> problem.
>> This also should only happen when cross-compiling.
>>
>
> This should fix the problem:
>
> http://hg.octave.org/mxe-octave/rev/0d23e586d872
>
> Michael.
>
> ---------
>
> With latest changeset 0d23e586d872, native mingw build:
>
> llvm[3]: Building llvm-config BuildVariables.inc file.
> llvm[3]: Compiling llvm-config.cpp for Release+Asserts build
> C:/MinGW/msys/1.0/home/jdonoghue/mxe-octave/tmp-llvm/llvm-3.1.src/tools/llvm
> -config/llvm-config.cpp:45:35: fatal error: LibraryDependencies.inc: No
> such
> file or directory compilation terminated.
> /bin/rm: cannot lstat
> `/usr/home/jdonoghue/mxe-octave/tmp-llvm/llvm-3.1.src/build/tools/llvm-confi
> g/Release+Asserts/llvm-config.d.tmp': No such file or directory
> make[3]: ***
> [/usr/home/jdonoghue/mxe-octave/tmp-llvm/llvm-3.1.src/build/tools/llvm-confi
> g/Release+Asserts/llvm-config.o] Error 1
> make[3]: Leaving directory
> `/home/jdonoghue/mxe-octave/tmp-llvm/llvm-3.1.src/build/tools/llvm-config'
> make[2]: *** [install] Error 1
>
>
>
> I don't do native MinGW compilation at the moment. Would you mind
> investigating in the Makefile's what's going on? It seems a file is not
> automatically generated (LibraryDependencies.inc). Alternatively, you
> might
> want to try to use cmake instead?
>
>
>
> Michael.
>
>
>
>   _____
>

> I will take a look.
>
> I originally got the native mingw build working by using the autotools as
> I
> gave up on the cmake stuff - I'm not a cmake fan, and the annoying trying
> to
> use Visual C message kept on coming up no matter what I seemed to do.

Did you build llvm by simply using configure - make make install entered
manually, rather than mk-dist?

I had similar troubles as you (Visual C++ interference and "llvm-config not
found") while running a native MXE build.

MXE configure has an option "--enable-jit" but the output from
'octave_config_info' from a cross build shows it just didn't work.
I think src/octave.mk has to be patched to (attempt to) build llvm support
(i.e., add the --enable-jit flag to the configure options there). I was
going to try that tonight (with an older MXE checkout) but I have little
hope -it didn't work last time I tried.

I've a patch pending that does that. I just need to complete my octave build first, then I'll submit it.

Michael.