From: Sven <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: itz@speakeasy.org, caml-list@inria.fr
Subject: Re: [Caml-list] Compiler ActiveDVI (CVS)
Date: Thu, 31 Jan 2002 12:45:23 +0100 [thread overview]
Message-ID: <20020131124523.B26246@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <20020126104546G.garrigue@kurims.kyoto-u.ac.jp>; from garrigue@kurims.kyoto-u.ac.jp on Sat, Jan 26, 2002 at 10:45:46AM +0900
On Sat, Jan 26, 2002 at 10:45:46AM +0900, Jacques Garrigue wrote:
> Hello Ian,
>
> > Jacques> If you start to mess around with the directories, this is not
> > Jacques> very helpful for anybody.
> >
> > Yes, it is: to people with experience on Debian, but none on Ocaml.
> > Which is exactly the sort of people that would install a binary
> > package, I think.
>
> The point is that the "right" way to compile an extension to ocaml is
> to use ocamlc, which will automatically add /usr/lib/ocaml to the
> include path. If the caml subdirectory is not there, this will not be
> very useful. Using ocamlc will also set properly some compilation
> flags for thread compliance, and make sure you can build a dll.
I can add a symlink then, if it is agreable.
> Since these headers will preferably _not_ be used by gcc directly,
> they don't need to be in the standard hierarchy.
Well, but people will look there.
> Another problem is that both ocaml's (unfortunately limited)
> documentation, and ocaml developpers base themselves on a standard
> installation. If you start messing around, you end-up with the kind of
> quiproquo we are seeing here.
I will have to patch the documentation then, or better yet add a note about
them.
> > The way I did it when I built Ocaml from sources was with a symlink,
> > so that it existed in both places.
>
> A symlink avoids all these problems. And if you do it yourself, you
> know that you're doing something nonstandard, and will no bother the
> developpers with this.
I will add a symlink in the next version of the package.
> > BTW, /usr/include/ocaml (to match the package name) would be a better
> > name.
>
> That seems a good idea too.
but will break all those #include <caml/xxx.h> :)))
5BTW, i agree, there are lot of caml left around in the ocaml distribution and
friends which could be changed to ocaml.
> By the way, all my comments do not intend to criticize the work of
> packagers. I know this is a hard task. I just hope we could end up
> with a better way to combine efforts.
Okay, i appreciate, i maybe don't all the time see things as fully as i
should, and may ignore problems that you or others may encounter.
I will add a symlink though, and everybody will be happy.
Friendly,
Sven Luther
-------------------
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-31 11:45 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
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 [this message]
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=20020131124523.B26246@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=itz@speakeasy.org \
/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