Jacques> The point is that the "right" way to compile an extension to
Jacques> ocaml is to use ocamlc, which will automatically add
Jacques> /usr/lib/ocaml to the include path. 

Interesting point.  I have hacked on a few extensions, but I _always_
just called gcc directly.  Somehow the fact that ocamlc is a full
driver just like gcc doesn't easily enter one's consciousness, I'm
afraid.  Also, when one uses things like autoconf and hairy makefile
rules, direct use of the C compiler is more conveient (think of all
the -ccopt stuff you'd have to pass...)

itz> The way I did it when I built Ocaml from sources was with a
itz> symlink, so that it existed in both places.

Jacques> A symlink avoids all these problems. And if you do it
Jacques> yourself, you know that you're doing something nonstandard,
Jacques> and will no bother the developpers with this.

I was suggesting that the link be a part of the package.  Users are
not supposed to touch /usr/include on Debian.

Best regards,

-- 
Ian Zimmerman, Oakland, California, U.S.A.
GPG: 433BA087  9C0F 194F 203A 63F7 B1B8  6E5A 8CA3 27DB 433B A087
In his own soul a man bears the source
from which he draws all his sorrows and his joys.
Sophocles.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr