From: Florian Douetteau <douet@clipper.ens.fr>
To: John Malecki <johnm@artisan.com>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] error messages to stdout?
Date: Sat, 19 Jan 2002 09:46:55 +0100 (MET) [thread overview]
Message-ID: <Pine.GSO.4.33.0201190927120.17215-100000@clipper.ens.fr> (raw)
In-Reply-To: <15431.6370.86918.38285@reggie.artisan.com>
>
> I'd be interested in the trampoline program.
>
> At the moment we are operating in a homogeneous computing environment.
> Sooner or later we will add some a different computer architecture to
> our pool and I was thinking about how to take advantage of compiling
> byte-code once and using it on all platforms. This has the advantage
> that a developer can compile once, on any one platform, and make that
> program immediately available on all other machine architectures.
>
> I'm not sure of the best way to do this. I was thinking of using the
> bash MACHTYPE environment variable and then install the byte-code
> program in /usr/local/bin but have the 1st line of that file say
>
> #! /usr/local/bin/ocamlrun.$MACHTYPE
>
An usual trick is to make the bytecode file
start with
#! /path_to_my_mach_type_dispatcher /usr/local/bin/ocamlrun
Executing the file will make the system execute:
"my_mach_type_dispatcher /usr/local/bin/ocamlrun bytecode-file-name"
my_mach_type_dispatcher can be a script as simple as:
#! /bin/sh
$1.$MACHTYPE $2
Another trick is to make each /usr/local/bin/ocamlrun.$MACHTYPE
be a symbol link to a script:
$0.$MACHTYPE $@
--
Florian Douetteau
-------------------
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
prev parent reply other threads:[~2002-01-21 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 5:12 Doug Bagley
2002-01-16 18:50 ` Warp
2002-01-16 19:06 ` Doug Bagley
2002-01-16 19:49 ` Remi VANICAT
2002-01-16 20:09 ` Doug Bagley
2002-01-17 18:33 ` John Malecki
2002-01-17 19:15 ` Doug Bagley
2002-01-19 8:11 ` Stefano Zacchiroli
2002-01-19 8:46 ` Florian Douetteau [this message]
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=Pine.GSO.4.33.0201190927120.17215-100000@clipper.ens.fr \
--to=douet@clipper.ens.fr \
--cc=caml-list@inria.fr \
--cc=johnm@artisan.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).