Re: LLVM/JIT on MacOS X

[Ben Abbott]

On Jun 11, 2014, at 5:45 AM, Stefan Mahr <address@hidden> wrote:

>>> Hi Ben,
>>> 
>>> your error message sounds like a incompatibility with newer LLVM versions 
>>> and should be fixed with my attached patch in this bug report: 
>>> http://savannah.gnu.org/bugs/?41061
>>> 
>>> As always, a rebased changeset to a more recent repository state can be 
>>> found here: http://inversethought.com/hg/octave-nkf/nkf-ready
>>> 
>>> Could you try the patch?
>>> 
>>> Stefan
>> 
>> Stefan, 
>> I'd like to try your changes but I'm not sure how to apply them right away 
>> ...
>> Can you make your changes into a patch that applies to the 3.8.2-rc1 tarball?
>> thanks,
>> c.
> 
> Carlo,
> The easiest way is to build from repository, update to @ or to rc-3-8-2-1 and 
> use hg transplant to apply the patch, e.g.
>  hg up -C rc-3-8-2-1
>  hg transplant -s http://inversethought.com/hg/octave-nkf 4a4edf0f2077
> Now you can build as usual
>  (./bootstrap; ./configure <options>; make )
> 
> 
> If you want to patch the tarball sources, try attached patch. It already 
> contains a generated configure script.
> 
> BR,
> Stefan
> 
> <llvm.diff>

>From the stable branch ...

$ patch -p1 < ~/Downloads/llvm.diff 
patching file config.in.h
patching file configure
Hunk #3 succeeded at 20250 (offset 3 lines).
Hunk #4 succeeded at 20268 with fuzz 2 (offset -4 lines).
Hunk #5 succeeded at 20290 (offset -4 lines).
patching file configure.ac
patching file libinterp/corefcn/jit-typeinfo.cc
patching file libinterp/corefcn/jit-util.h
patching file libinterp/corefcn/pt-jit.cc
patching file libinterp/corefcn/pt-jit.h
patching file m4/acinclude.m4
patching file m4/libtool.m4
Hunk #2 succeeded at 1326 with fuzz 2 (offset -7 lines).
Hunk #3 succeeded at 1348 (offset -7 lines).
patching file Makefile.in
Reversed (or previously applied) patch detected!  Assume -R? [n] 
Apply anyway? [n] 
Skipping patch.
2 out of 2 hunks ignored -- saving rejects to file Makefile.in.rej
make -j4
<snip>
</snip>
Undefined symbols for architecture x86_64:
  "llvm::verifyModule(llvm::Module const&, llvm::VerifierFailureAction, 
std::basic_string<char, std::char_traits<char>, std::allocator<char> >*)", 
referenced from:
      tree_jit::optimize(llvm::Function*)      in 
libcorefcn.a(corefcn_libcorefcn_la-pt-jit.o)
  "llvm::raw_fd_ostream::raw_fd_ostream(char const*, std::basic_string<char, 
std::char_traits<char>, std::allocator<char> >&, unsigned int)", referenced 
from:
      tree_jit::optimize(llvm::Function*)      in 
libcorefcn.a(corefcn_libcorefcn_la-pt-jit.o)
  "llvm::ExecutionEngine::createJIT(llvm::Module*, std::basic_string<char, 
std::char_traits<char>, std::allocator<char> >*, llvm::JITMemoryManager*, 
llvm::CodeGenOpt::Level, bool, llvm::Reloc::Model, llvm::CodeModel::Model)", 
referenced from:
      tree_jit::initialize()      in 
libcorefcn.a(corefcn_libcorefcn_la-pt-jit.o)
ld: symbol(s) not found for architecture x86_64

I'm running llvm-3.3, and get the same result when I first bootstrap and 
configure.

Ben