From: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Building a custom compiler environment
Date: Tue, 15 Nov 2005 11:36:39 +1300 [thread overview]
Message-ID: <ad8cfe7e0511141436y4f7a6e7evaa2fcd42b2f5fe3@mail.gmail.com> (raw)
In-Reply-To: <ad8cfe7e0511132238m5aeac1c7t11be60971ac68dfa@mail.gmail.com>
I also need to ask: why are the primitives built INTO the compiler? Is
there any sound explanation for this?
One reason I could think of is to force the linker to keep those
symbols in the final output file (when using -output-obj). But if
they're not used, then why do they need to be present? For Dynlink to
work correctly?
This seems to be the -one- thing to make building my custom compiler
environment not work without requiring a customised ocamlc (with less
primitives builtin).
Jonathan
next prev parent reply other threads:[~2005-11-14 22:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 3:01 Jonathan Roewen
2005-11-13 4:05 ` Jonathan Roewen
2005-11-13 11:09 ` Gerd Stolpmann
2005-11-14 6:38 ` Jonathan Roewen
2005-11-14 22:36 ` Jonathan Roewen [this message]
2005-11-15 4:10 ` skaller
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=ad8cfe7e0511141436y4f7a6e7evaa2fcd42b2f5fe3@mail.gmail.com \
--to=jonathan.roewen@gmail.com \
--cc=caml-list@yquem.inria.fr \
/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).