From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 1EC6F7EE99 for ; Tue, 7 Jan 2014 18:25:32 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of john@coherentgraphics.co.uk) identity=pra; client-ip=188.64.184.40; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="john@coherentgraphics.co.uk"; x-sender="john@coherentgraphics.co.uk"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of john@coherentgraphics.co.uk) identity=mailfrom; client-ip=188.64.184.40; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="john@coherentgraphics.co.uk"; x-sender="john@coherentgraphics.co.uk"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@bluechip4.ukhost4u.com) identity=helo; client-ip=188.64.184.40; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="john@coherentgraphics.co.uk"; x-sender="postmaster@bluechip4.ukhost4u.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhMDACQ4zFK8QLgoemdsb2JhbABZg0O6O4ESFg4BAQsHDQk8giUBAQEDAThAAQULCwcRCRYPCQMCAQIBRQYOIIdhDAHEJxePBAeENwSeXI59 X-IPAS-Result: AhMDACQ4zFK8QLgoemdsb2JhbABZg0O6O4ESFg4BAQsHDQk8giUBAQEDAThAAQULCwcRCRYPCQMCAQIBRQYOIIdhDAHEJxePBAeENwSeXI59 X-IronPort-AV: E=Sophos;i="4.95,619,1384297200"; d="scan'208";a="43880983" Received: from bluechip4.ukhost4u.com ([188.64.184.40]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Jan 2014 18:25:31 +0100 Received: from [46.64.58.255] (port=57392 helo=[192.168.1.66]) by bluechip4.ukhost4u.com with esmtpsa (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) (Exim 4.82) (envelope-from ) id 1W0aPC-001ywa-Tc; Tue, 07 Jan 2014 17:25:30 +0000 Message-ID: <52CC3885.7000104@coherentgraphics.co.uk> Date: Tue, 07 Jan 2014 17:25:25 +0000 From: John Whitington User-Agent: Postbox 3.0.8 (Macintosh/20130427) MIME-Version: 1.0 To: "caml-list@inria.fr" CC: David Allsopp References: <52CBE924.4070102@coherentgraphics.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bluechip4.ukhost4u.com X-AntiAbuse: Original Domain - inria.fr X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - coherentgraphics.co.uk X-Get-Message-Sender-Via: bluechip4.ukhost4u.com: authenticated_id: john@coherentgraphics.co.uk Subject: Re: [Caml-list] Adding functions to Pervasives 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/