From: skaller <skaller@users.sourceforge.net>
To: caml-list <caml-list@inria.fr>
Subject: [Caml-list] autocompile
Date: 11 Apr 2004 21:01:39 +1000 [thread overview]
Message-ID: <1081681298.20677.396.camel@pelican> (raw)
I have this annoying problem sometimes:
The files /usr/local/lib/ocaml/pervasives.cmi
and /usr/local/lib/ocaml/lablgtk2/gdk.cmi make inconsistent assumptions
over interface Pervasives
Of course the problem is that I installed a new version
of Ocaml from a CVS build, but didn't rebuild lablgtk2.
Obviously, just saying 'reinstall lablgtk2' isn't
an answer: it's in the standard distribution location,
the installation process should handle that automatically.
I was thinking: why not build the dependencies
into the compiled files, so if a compiled file is
out of date it can be rebuilt automatically?
Perhaps a switch would enable the autorebuild:
I wouldn't suggest doing it by default.
One would need to put the files depended on,
including the path to the compiler, along with
timestamps, and also put the command line used
for the compilation (possibly with absolute pathnames
replacing the ones actually typed in).
Also, when installing Ocaml, it would be interesting
to have a make target that rebuild any installed libraries,
since a user recompilation of a system library would
fail due to lack of permissions.
Does findlib already do this kind of thing?
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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 reply other threads:[~2004-04-11 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 11:01 skaller [this message]
2004-04-12 16:38 ` Xavier Leroy
2004-04-12 17:38 ` skaller
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=1081681298.20677.396.camel@pelican \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.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