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 UAA31288; Sun, 30 Mar 2003 20:13:36 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id UAA31220 for ; Sun, 30 Mar 2003 20:13:33 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from opus.davidb.org (66-75-152-1.san.rr.com [66.75.152.1]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id h2UIDSX01434; Sun, 30 Mar 2003 20:13:32 +0200 (MET DST) Received: from davidb by opus.davidb.org with local (Exim 3.31 #1 (Debian)) id 18zhIz-0003uX-00; Sun, 30 Mar 2003 10:13:17 -0800 Date: Sun, 30 Mar 2003 10:13:17 -0800 From: David Brown To: Xavier Leroy Cc: Wheeler Ruml , caml-list@inria.fr Subject: Re: [Caml-list] VxWorks? mailing list? Message-ID: <20030330181317.GA15002@opus.davidb.org> References: <16003.43377.636464.160830@katsura.parc.xerox.com> <20030330122643.D22539@pauillac.inria.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030330122643.D22539@pauillac.inria.fr> User-Agent: Mutt/1.4i X-Spam: no; 0.00; caml-list:01 posix:01 threads:01 -output-obj:01 compiler:01 byte:01 bytecode:01 supported:01 0200,:01 trivial:01 native-code:02 compile:02 harder:02 address:96 dave:03 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk On Sun, Mar 30, 2003 at 12:26:43PM +0200, Xavier Leroy wrote: > I have no experience with VxWorks, but from their Web site it appears > to be POSIX-compliant. If so, chances are very high that the bytecode > interpreter will compile and work right out of the box. For the > native-code compiler, the porting effort can range from the trivial > (e.g. one of the supported configurations just happens to work) to the > fairly hard (e.g. a new code generator has to be written). It's not > possible to say without more details on the target platform and > environment. It might be a little harder than just compiling to get the byte code interpreter working. It depends on the byte-code interpreters demand for memory management. Most VxWorks systems I use just have a single address space. VxWorks can be thought of as a single task on a Posix system with multiple threads. It also don't have a normal shell and that kind of stuff, so the code would have to be byte-compiled on one machine and moved over. It would probably be easiest to use -output-obj to have the linker include the object. Cross compilation didn't look that easy last time I thought about trying to do it. Dave ------------------- 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