From: Alain Frisch <alain.frisch@inria.fr>
To: Jeff Henrikson <jehenrik@yahoo.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] nonresolved .cma files and errors
Date: Wed, 11 Apr 2007 10:04:10 +0200 [thread overview]
Message-ID: <461C967A.6000007@inria.fr> (raw)
In-Reply-To: <461C50C7.6090802@yahoo.com>
Jeff Henrikson wrote:
> I recently had a shocking realization about why some of my experiments
> with camlp4 weren't compiling. I had been linking camlp4.cma, which was
> the old name of the library. Now camlp4.cma doesn't exist and there are
> multiple flavors Camlp4xxx.cma where the xxx is the same flavor notation
> of the the preprocessor binaries. So the trouble is, why was linking
> such a library not a fatal? Apparently all missing .cma and .cmo files
> passed on the command line are considered non-errors.
.cma and .cmo files are not used during compilation. They make sense
only for link operations (including -pack and -a). One might argue that
the compiler should issue a warning when useless .cma and .cmo are given
on the command line.
-- Alain
next prev parent reply other threads:[~2007-04-11 8:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-11 3:06 Jeff Henrikson
2007-04-11 6:58 ` [Caml-list] " Martin Jambon
2007-04-11 8:04 ` Alain Frisch [this message]
2007-04-12 6:42 ` Jeff Henrikson
2007-04-12 7:05 ` Alain Frisch
2007-04-11 11:35 ` Nicolas Pouillard
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=461C967A.6000007@inria.fr \
--to=alain.frisch@inria.fr \
--cc=caml-list@inria.fr \
--cc=jehenrik@yahoo.com \
/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).