caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ian Zimmerman <itz@speakeasy.org>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Compiler ActiveDVI (CVS)
Date: 25 Jan 2002 18:00:33 -0800	[thread overview]
Message-ID: <86lmelna66.fsf@speakeasy.org> (raw)
In-Reply-To: <20020126104546G.garrigue@kurims.kyoto-u.ac.jp>


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


  reply	other threads:[~2002-01-26  2: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
2002-01-26  0:49       ` Ian Zimmerman
2002-01-26  1:45         ` Jacques Garrigue
2002-01-26  2:00           ` Ian Zimmerman [this message]
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=86lmelna66.fsf@speakeasy.org \
    --to=itz@speakeasy.org \
    --cc=caml-list@inria.fr \
    --cc=garrigue@kurims.kyoto-u.ac.jp \
    /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;
as well as URLs for NNTP newsgroup(s).