Databases
StackOverflow2013
Postsdbo
POOcaml + LLVM under cygwin (or, more generally, statically linking with C object files under cygwin)?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POOcaml + LLVM under cygwin (or, more generally, statically linking with C object files under cygwin)?
    text
    copied!<p>The tests for the Ocaml bindings (which are automatically installed if you make LLVM with Ocaml already installed) all fail under cygwin, and when I try to create even the most trivial program, I get the same error that all of the built-in tests fail on: </p> <pre><code>&gt; ocamlopt -I +llvm-2.8 -cc g++ llvm.cmxa llvm_bitwriter.cmxa llvm_trivial.ml -o llvm_trivial /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x14a): undefined reference to `_flexdll_dlerror' /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x177): undefined reference to `_flexdll_dlopen' /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x193): undefined reference to `_flexdll_dlopen' /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x1a2): undefined reference to `_flexdll_dlsym' /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x1bc): undefined reference to `_flexdll_dlsym' /usr/lib/ocaml/libasmrun.a(unix.o):unix.c:(.text+0x1cf): undefined reference to `_flexdll_dlclose' collect2: ld returned 1 exit status File "caml_startup", line 1, characters 0-1: Error: Error during linking </code></pre> <p>Googling around indicates that <a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/01/20fa3986427e9a20279dfbab9196cc6c.en.html" rel="nofollow">this isn't LLVM specific</a>, and that other people have the same problem, but I couldn't find a solution. I have flexdll installed. Am I just not referencing it correctly?</p> <p>This works for me on my linux system, so I think it's something particular to what I'm doing on cygwin. Any suggestions?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload