From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA24475; Mon, 21 Jan 2002 11:11:06 +0100 (MET) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id LAA24447 for caml-list@pauillac.inria.fr; Mon, 21 Jan 2002 11:11:06 +0100 (MET) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id JAA03328 for ; Sat, 19 Jan 2002 09:46:57 +0100 (MET) Received: from nef.ens.fr (nef.ens.fr [129.199.96.32]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id g0J8kuj08939 for ; Sat, 19 Jan 2002 09:46:56 +0100 (MET) Received: from clipper.ens.fr (clipper-gw.ens.fr [129.199.1.22]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g0J8kue84056 ; Sat, 19 Jan 2002 09:46:56 +0100 (CET) Received: from localhost (douet@localhost) by clipper.ens.fr (8.9.2/jb-1.1) id JAA22529 ; Sat, 19 Jan 2002 09:46:55 +0100 (MET) Date: Sat, 19 Jan 2002 09:46:55 +0100 (MET) From: Florian Douetteau To: John Malecki cc: Subject: Re: [Caml-list] error messages to stdout? In-Reply-To: <15431.6370.86918.38285@reggie.artisan.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk > > 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