From: Markus Mottl <markus.mottl@gmail.com>
To: OCaml <caml-list@inria.fr>
Cc: Yaron Minsky <yminsky@janestcapital.com>
Subject: Bootstrapping problem with patched compiler
Date: Fri, 8 Jul 2005 15:02:45 -0400 [thread overview]
Message-ID: <20050708190245.GA21352@quant3.janestcapital.quant> (raw)
Hi,
I have run into linking problems trying to bootstrap OCaml patched
with more primitives in the standard library. The patch changes
the Printexc-module in the standard library and refers to external
functions, which were added to byterun/printexc.c (as CAMLprim).
byterun/Makefile has been changed as required (variable PRIMS) to include
byterun/printexc.c now when computing primitives.
According to a post from Xavier some time ago the right way to bootstrap
the compiler with such changes is as follows:
- start with pristine OCaml sources
- do "make world"
- perform your changes
- do "make all" (NOT "make world")
- do "make bootstrap" to make sure everything is OK.
Unfortunately, this does not work for me. Here is the last error message,
which pops up after "make all":
make[2]: Entering directory `/tmp/ocaml/otherlibs/labltk/lib'
../../../ocamlcomp.sh -verbose -linkall -o labltktop -I ../support \
-I ../../../toplevel toplevellib.cma \
-I ../labltk -I ../camltk labltk.cma \
-I ../../unix unix.cma \
-I ../../str str.cma \
topstart.cmo
Files ../../../toplevel/toplevellib.cma(Topmain) and
../../../stdlib/stdlib.cma(Printexc) make inconsistent assumptions over
interface Printexc
Since I don't understand all dependencies of the build process, maybe one
of the developers could give me a hint where the bootstrapping failed? -
Thanks a lot!
Best regards,
Markus
--
Markus Mottl markus.mottl@gmail.com http://www.ocaml.info
next reply other threads:[~2005-07-08 19:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 19:02 Markus Mottl [this message]
2005-07-08 22:10 ` [Caml-list] " Jacques Garrigue
2005-07-11 15:28 ` Markus Mottl
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=20050708190245.GA21352@quant3.janestcapital.quant \
--to=markus.mottl@gmail.com \
--cc=caml-list@inria.fr \
--cc=yminsky@janestcapital.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).