caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Joel Reymont <joelr1@gmail.com>
To: micha <micha-1@fantasymail.de>
Cc: Xavier Leroy <Xavier.Leroy@inria.fr>, Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] beta-test of OCaml 3.10.0
Date: Wed, 7 Mar 2007 14:12:32 +0000	[thread overview]
Message-ID: <77A9A6F3-6634-4C51-84A7-844E8A3FE274@gmail.com> (raw)
In-Reply-To: <20070307150838.3bb7b7ae@localhost>


On Mar 7, 2007, at 2:08 PM, micha wrote:

> building with "./build/fastworld.sh" doesn't work here (Etch,  
> 2.6.20.1,
> Athlon XP)

You need to do 'make clean' beforehand but I still get this on Mac  
OSX 10.4.8 Intel:

Error while linking bytecomp/symtable.cmo:
Reference to undefined global `Runtimedef'
Exit code 2 while executing this command:
   boot/ocamlrun ./ocamlc -nostdlib -g -I stdlib  
myocamlbuild_config.cmo utils/config.cmo bytecomp/bytesections.cmo  
utils/misc.cmo bytecomp/dll.cmo parsing/linenum.cmo utils/ 
terminfo.cmo utils/warnings.cmo parsing/location.cmo parsing/ 
longident.cmo typing/ident.cmo typing/path.cmo typing/primitive.cmo  
typing/types.cmo typing/btype.cmo typing/predef.cmo typing/ 
datarepr.cmo utils/tbl.cmo typing/subst.cmo utils/clflags.cmo utils/ 
consistbl.cmo typing/env.cmo bytecomp/lambda.cmo bytecomp/ 
instruct.cmo bytecomp/opcodes.cmo bytecomp/meta.cmo bytecomp/ 
symtable.cmo utils/ccomp.cmo bytecomp/bytelink.cmo bytecomp/ 
bytelibrarian.cmo bytecomp/switch.cmo bytecomp/bytegen.cmo bytecomp/ 
printlambda.cmo typing/ctype.cmo typing/typedtree.cmo bytecomp/ 
typeopt.cmo typing/parmatch.cmo bytecomp/matching.cmo bytecomp/ 
translobj.cmo bytecomp/translcore.cmo bytecomp/translclass.cmo typing/ 
mtype.cmo typing/oprint.cmo typing/printtyp.cmo bytecomp/ 
translmod.cmo bytecomp/emitcode.cmo typing/includeclass.cmo typing/ 
includecore.cmo typing/includemod.cmo typing/stypes.cmo typing/ 
typetexp.cmo typing/typecore.cmo typing/typedecl.cmo typing/ 
typeclass.cmo typing/typemod.cmo bytecomp/bytepackager.cmo bytecomp/ 
printinstr.cmo bytecomp/simplif.cmo driver/pparse.cmo parsing/ 
syntaxerr.cmo parsing/parser.cmo parsing/lexer.cmo parsing/parse.cmo  
parsing/printast.cmo typing/unused_var.cmo driver/compile.cmo driver/ 
errors.cmo driver/main_args.cmo driver/main.cmo -o driver/main.byte

--
http://wagerlabs.com/






  reply	other threads:[~2007-03-07 14:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-07 13:10 Xavier Leroy
2007-03-07 14:08 ` [Caml-list] " micha
2007-03-07 14:12   ` Joel Reymont [this message]
2007-03-07 14:54     ` micha
2007-03-07 15:00       ` Nicolas Pouillard
2007-03-07 15:01     ` Nicolas Pouillard
2007-03-07 15:17       ` Joel Reymont
2007-03-07 15:39 ` Vu Ngoc San
2007-03-07 15:47   ` Nicolas Pouillard
2007-03-10 21:24 ` Paul Snively
2007-03-12 11:17 ` Sven Luther
2007-03-16  8:54 ` Mike Lin
2007-03-16  8:58   ` Nicolas Pouillard
2007-03-16  9:06   ` Gabriel Kerneis
2007-03-16  9:19   ` Olivier Andrieu
2007-03-17 17:46 ` Peter Halacsy
2007-03-17 17:54   ` Nicolas Pouillard
2007-03-18  7:57     ` ocamlbuild and ocamlfind / was: " Peter Halacsy
2007-03-18 10:04       ` Nicolas Pouillard
2007-03-20 20:00 ` Oliver Bandel
2007-03-07 15:53 ocamlbuild is VERY nifty Joel Reymont
2007-03-07 20:55 ` [Caml-list] beta-test of OCaml 3.10.0 Jon Harrop

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=77A9A6F3-6634-4C51-84A7-844E8A3FE274@gmail.com \
    --to=joelr1@gmail.com \
    --cc=Xavier.Leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=micha-1@fantasymail.de \
    /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).