caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Whitington <john@coherentgraphics.co.uk>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Cc: David Allsopp <dra-news@metastack.com>
Subject: Re: [Caml-list] Adding functions to Pervasives
Date: Tue, 07 Jan 2014 17:25:25 +0000	[thread overview]
Message-ID: <52CC3885.7000104@coherentgraphics.co.uk> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D9E0297FE7@Remus.metastack.local>

Hi,

David Allsopp wrote:
> Does your custom OCaml bootstrap? Wondering if the wrong header gets installed - looking at typing/env.ml, your most likely problem is a mismatch between pervasives.cmi and pervasives.cmo

Yes, the new OCaml bootstraps successfully at the first attempt.

I'll have a look at typing/env.ml -- thanks for the suggestion.

> There's also the -nopervasives switch to ocamlopt (it's undocumented, but I think you'll find it does almost exactly what it says on the tin!) which might yield clearer code?

How do you mean? I'm adding functions to Pervasives because I want these 
patches to eventually be applied to trunk (I'm playing with solutions to 
Bug 5443).

I had assumed I was running into a common problem, since functions get 
added to Pervasives from time to time.

For now, I'll add these functions in another module and continue with 
the rest of the patch.

Thanks,

-- 
John Whitington
Director, Coherent Graphics Ltd
http://www.coherentpdf.com/


      parent reply	other threads:[~2014-01-07 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07 11:46 John Whitington
     [not found] ` <E51C5B015DBD1348A1D85763337FB6D9E0297FE7@Remus.metastack.local>
2014-01-07 17:25   ` John Whitington [this message]

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=52CC3885.7000104@coherentgraphics.co.uk \
    --to=john@coherentgraphics.co.uk \
    --cc=caml-list@inria.fr \
    --cc=dra-news@metastack.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).