octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58689] [MXE Octave] Update mesa to use meson


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #58689] [MXE Octave] Update mesa to use meson as (native) build tool
Date: Wed, 8 Jul 2020 11:00:34 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36 Edg/83.0.478.58

Follow-up Comment #16, bug #58689 (project octave):

I see the same as you. In particular:

./usr/x86_64-w64-mingw32/bin/x86_64-w64-mingw32-llvm-config  --system-libs
-lz -lrt -ldl -ltinfo -lpthread -lm -lxml2


Similarly for the shared libraries (which mesa should probably link to
anyway):

./usr/x86_64-w64-mingw32/bin/x86_64-w64-mingw32-llvm-config  --system-libs
--link-shared
llvm-config: error: libLLVM-6.0.so is missing


That is not what a Windows dynamic library would be named. (It should be
looking for something named "LLVM.dll" or similarly.)

Both looks like a bug in llvm to me. IIUC, the native llvm-config that is
built when cross-compiling llvm should help other applications that want to be
cross-compiled. (But I may have misunderstood.)

Maybe that has been fixed in a newer version of llvm.

If I recall correctly, we keep llvm at the current version (6.1) for the JIT
compiler in Octave. But the JIT compiler has limited benefit as it is right
now anyway, and no one seems to use it currently (more so in cross-builds). 
So, do you think it would be ok to try to update llvm (and maybe breaking the
option to compile Octave with JIT compiler in MXE)?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58689>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]