From: Hendrik Tews <tews@os.inf.tu-dresden.de>
To: caml-list@inria.fr
Subject: ocamlbuild: full path for camlp4 preprocessors?
Date: Tue, 24 Aug 2010 10:29:08 +0200 [thread overview]
Message-ID: <19571.33492.589609.728522@blau.inf.tu-dresden.de> (raw)
Hi,
I have another ocamlbuild question: How can I tell ocamlbuild to
use the full path for the camlp4 preprocessors?
I just compiled ocaml 3.12 to test if it compiles my software. So
I do
/soft/ocaml-3.12.0/bin/ocamlbuild target.native
and ocamlbuild is clever enough to prefix all commands with
/soft/ocaml-3.12.0/bin to make sure the 3.12 compiler
is used. But then comes this file that needs camlp4 and
ocamlbuild runs
/soft/ocaml-3.12.0/bin/ocamldep.opt -pp camlp4orf -modules xx.ml > ...
which of course fails because camlp4orf is version 3.11.2 from
/usr/bin.
How can I tell ocamlbuild to also use the full path for camlp4
preprocessors?
(I could put /soft/ocaml-3.12.0/bin into PATH, but there should
be a way to solve this problem without changing PATH: It should
be possible to run ocamlbuild without putting the ocaml-bin-dir
into PATH)
Thanks,
Hendrik Tews
reply other threads:[~2010-08-24 8:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19571.33492.589609.728522@blau.inf.tu-dresden.de \
--to=tews@os.inf.tu-dresden.de \
--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