From: David MENTRE <dmentre@linux-france.org>
To: Kenneth Knowles <kknowles@uclink.berkeley.edu>
Cc: ijtrotts@ucdavis.edu, caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] Development versions: ocamlconf, ASPCC
Date: Wed, 03 Mar 2004 20:56:27 +0100 [thread overview]
Message-ID: <87wu611z84.fsf@linux-france.org> (raw)
In-Reply-To: <20040303062539.GA27167@tallman.kefka.frap.net> (Kenneth Knowles's message of "Tue, 2 Mar 2004 22:25:39 -0800")
Hello Kenneth,
Kenneth Knowles <kknowles@uclink.berkeley.edu> writes:
> The configure script (actually configure.mlc, for technical reasons,
> and the configure script is a shell wrapper around `ocaml configure.mlc`) is
> also plain text ocaml, but with additional code copied into it.
So the produced configure script is an OCaml program that needs the
ocaml environment to run? I share all the objections against autoconf,
but at least it produces a simple sh script that can run on any (unix)
system. The role of a configure script is also to find the ocaml
compiler or warn that it is a requirement. That's said, I admit that if
somebody intends to compile an OCaml program, he probably have ocaml on
his machine. But that's still introduce a dependency *before* running
the configure script of which role is to find dependencies.
My 2 cents,
Yours,
d.
--
David Mentré <dmentre@linux-france.org>
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-03-03 19:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 1:47 Kenneth Knowles
2004-03-03 5:16 ` Issac Trotts
2004-03-03 6:25 ` Kenneth Knowles
2004-03-03 19:53 ` Issac Trotts
2004-03-03 23:06 ` Kenneth Knowles
2004-03-03 19:56 ` David MENTRE [this message]
2004-03-03 20:29 ` Issac Trotts
2004-03-03 22:36 ` Kenneth Knowles
2004-03-11 11:09 ` Markus Mottl
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=87wu611z84.fsf@linux-france.org \
--to=dmentre@linux-france.org \
--cc=caml-list@inria.fr \
--cc=ijtrotts@ucdavis.edu \
--cc=kknowles@uclink.berkeley.edu \
/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