From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: luther@dpt-info.u-strasbg.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiler ActiveDVI (CVS)
Date: Sat, 26 Jan 2002 07:59:21 +0900 [thread overview]
Message-ID: <20020126075921Y.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <20020125151002.B16553@dpt-info.u-strasbg.fr>
From: Sven <luther@dpt-info.u-strasbg.fr>
> > > creating cache ./config.cache
> > > checking your compiler package... version 3.04 at /usr/lib/ocaml
> >
> > Thus. That's the directory where ocaml has installed its library files (It
> > is bound to CAMLDIR in Makefile.config of advi). Thus, ocaml should have
> > copied the files (mlvalues.h, alloc.h, etc.) in the subdirectory
> > $CAMLDIR/caml.
>
> No, the include files are in /usr/include/caml on a debian system as the FHS
> mandates.
That doesn't seem to be a good thing to do.
Objective Caml has only one standard: a unique distribution. If you
start to mess around with the directories, this is not very helpful
for anybody. There is no way a library developper can find the path of
the caml include files, other than expecting them to be in the
standard place, under the library directory. Usually you just call
them by <caml/mlvalues.h>, and your scheme with still work, but if
anybody chooses to do -I`ocaml -where`/caml , which is supposed to be
correct, then it breaks.
And what are you doing with caml-light header files ?
By the way, FHS or not, glib puts parts of its headers in
/usr/local/lib/grealizelib/include, which seems to be pretty similar to what
ocaml does (I noticed that righteous FreeBSD mainteners are moving them
back to /usr/local/include/glib12...)
And these headers will only be used by ocaml programs, this is not
just a standard C library.
Just a comment.
Cheers,
Jacques Garrigue
-------------------
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
next prev parent reply other threads:[~2002-01-25 23:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-25 7:23 David Marsal
2002-01-25 11:14 ` Sven
2002-01-25 13:56 ` Jun P.FURUSE
2002-01-25 14:07 ` Sven
2002-01-25 14:10 ` Sven
2002-01-25 13:16 ` Didier Remy
2002-01-25 14:10 ` Sven
2002-01-25 22:59 ` Jacques Garrigue [this message]
2002-01-26 0:49 ` Ian Zimmerman
2002-01-26 1:45 ` Jacques Garrigue
2002-01-26 2:00 ` Ian Zimmerman
2002-01-31 11:45 ` Sven
2002-01-31 11:41 ` Sven
2002-01-25 19:18 ` Alan Schmitt
2002-01-25 22:40 ` [Caml-list] CDK support Jacques Garrigue
2002-01-26 8:06 ` Alan Schmitt
2002-01-28 8:53 ` Fabrice Le Fessant
2002-01-25 9:16 [Caml-list] Compiler ActiveDVI (CVS) Roberto Di Cosmo
2002-01-25 9:58 ` Christophe Raffalli
2002-01-27 21:27 ` Roberto Di Cosmo
2002-01-28 16:10 ` Didier Remy
2002-01-31 11:47 ` Sven
2002-01-31 21:30 ` Alan Schmitt
2002-01-29 13:45 ` Didier Remy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020126075921Y.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox