[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2005-01-12 (09:01) |
From: | Olivier Andrieu <andrieu@i...> |
Subject: | Re: [Caml-list] glibc and ocaml/libasmrun.a |
> Radu Grigore [Wed, 12 Jan 2005]: > Hello, > > I have trouble distributing a self contained executable. > > Two users reported "collect_events: /lib/i686/libc.so.6: version > `GLIBC_2.3' not found". I do not have any control over their system, > so I tried to link statically against glibc by using: > > ocamlopt -ccopt -static collect_events.ml > > I get: > > /usr/local/lib/ocaml/libasmrun.a(unix.o)(.text+0x241): In function > `caml_dlopen': > warning: Using 'dlopen' in statically linked applications requires > at runtime the shared libraries from the glibc version used for > linking This means the runtime (libasmrun.a) contains calls to dlopen(). Now I'm not sure why there are dlopen's in the native (ocamlopt) runtime. I thought only the bytecode one is using dlopen (to dynamically link stub libraries). If that is correct (ie the native runtime doesn't actually use dlopen) then I guess you can ignore the warning. -- Olivier