]> Rolf Wester wrote: > Hi, > > I have a c++-library compiled with the icc-compiler, a c-interface to this > library (cinterface.h and cinterface.cpp) and stubs files generated using > camlidl (ocaml_opt.idl, ocaml_opt_stubs.cpp, ocaml_opt.ml, ocaml_opt.mli). > I try to build a custom toplevel with: > > ocamlmktop -custom -thread unix.cma str.cma bigarray.cma nums.cma \ > threads.cm graphics.cma \ > ../cinterface/cinterface.o ocaml_opt_stubs.o ocaml_opt.cmo \ > /usr/lib/libexpat.a \ > /usr/lib/libdfftw.a \ > /opt/intel/compiler60/ia32/lib/libcxa.so \ > /lib/ld-linux.so \ > ../lib/libopt.a \ > -cclib -ldl -cclib -lpthread -cclib -lutil -cclib -lm -cclib -lc \ > -o ocaml_opt > ... Apparently no Jedi Camler has answered your question yet, so I'll give you my opinion FWIW. I believe you are linking the files in the wrong order. All references in a given file provided as input to the ocaml compiler during the linking phase must be resolved in the files *preceding* it on the command line. The fact that the linker is unable to resolve such "banal" references as operator new probably indicates that libcxa.so should be placed towards the beginning of the cammand line. Anyhow, try to work out a dependency DAG between the different linking modules, in order to discover precisely what conflict(s) is(are) causing the above mentioned problem. I hope this helps. Otherwise, you'll have to wait for one of the Jedis to come along and solve the problem. Alex ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners