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 mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by sympa.inria.fr (Postfix) with ESMTPS id 23D517EC41 for ; Tue, 16 Oct 2012 16:59:37 +0200 (CEST) Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of anthony.tavener@gmail.com) identity=pra; client-ip=209.85.223.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="anthony.tavener@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail1-smtp-roc.national.inria.fr: domain of anthony.tavener@gmail.com designates 209.85.223.182 as permitted sender) identity=mailfrom; client-ip=209.85.223.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="anthony.tavener@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail1-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ie0-f182.google.com) identity=helo; client-ip=209.85.223.182; receiver=mail1-smtp-roc.national.inria.fr; envelope-from="anthony.tavener@gmail.com"; x-sender="postmaster@mail-ie0-f182.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjADAGZ1fVDRVd+2lGdsb2JhbABFrgaJIwGITwgjAQEBAQkJCwkSKYIgAQEBAwESAiwBGxILAQMMBgUEBxohIgERAQUBChIZEhCHTwEDCQYLnGgJA4wogWyBCoUZChknAwpZiHUBBQyLQ4Y9A4hYjROBFY08FimELg X-IronPort-AV: E=Sophos;i="4.80,593,1344204000"; d="scan'208";a="177476503" Received: from mail-ie0-f182.google.com ([209.85.223.182]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 16 Oct 2012 16:59:36 +0200 Received: by mail-ie0-f182.google.com with SMTP id k10so16837908iea.27 for ; Tue, 16 Oct 2012 07:59:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VI7LpcEhMxhUimZahlrEMe0sEJVRxwQow63LDL6iAms=; b=yYKEiQT51mYR9SskxHoj2d3fMhuDELK5I15aHxqE6B5wEVmI+Ol24C2rf9UZznnmNJ 5sUu+cKtUH408hBk2l5vtNO7GChKzeXo2cI8CFlCxjPPmbds1ew9PXQ5RODP46+4Hdvt IurXigL731QdMFcvlCjjJTGMXcKvW9IUImAw2j5j98l4ETEJ7KfRwJGz+wgyfxfP8hfj WxATSBFr37pVlshBrEaKUuUPc2cgtr2vApVEqJ0EwNHZ6dSOQCK76DhU87fvqga0Ylui x9Rl94WwASMeApfC5313yiHe6+ySljs/9cd3c0qV9PM7Mnul8PSz5avT9ImbUkFMAyL5 h8yQ== MIME-Version: 1.0 Received: by 10.50.219.229 with SMTP id pr5mr12382611igc.59.1350399576195; Tue, 16 Oct 2012 07:59:36 -0700 (PDT) Received: by 10.42.196.71 with HTTP; Tue, 16 Oct 2012 07:59:36 -0700 (PDT) In-Reply-To: <20121016070618.80750.qmail@www1.g3.pair.com> References: <20121016070618.80750.qmail@www1.g3.pair.com> Date: Tue, 16 Oct 2012 08:59:36 -0600 Message-ID: From: Anthony Tavener To: oleg@okmij.org Cc: christophe.raffalli@univ-savoie.fr, caml-list@inria.fr Content-Type: multipart/alternative; boundary=f46d040716990b432504cc2e6743 Subject: Re: [Caml-list] Re: ocaml 3.12.1 and delimcc --f46d040716990b432504cc2e6743 Content-Type: text/plain; charset=ISO-8859-1 Thank-you Oleg, for limiting my hunt for a red-herring. :) I only looked through the web-svn changes to 3.12.1 and nothing stood out as a problematic change... I should have installed 3.12.1 to try it out. With 4.00.0 (and this is a new machine with no prior installs) I pulled the corresponding files from 4.0 source into an ocaml-byterun-4.00 directory, and the native test segfaults. Just now I tried pointing to the 3.11 directory and it also segfaults. I expect going to 4.x there's been a change of some significance for delimcc. I'm not using GADTs or other 4.x features yet, and delimcc is more important to me -- so I'm happy enough using 3.12 while casually prodding at delimcc+4.x. -Tony P.S. Thanks for the nifty gadgets! (I keep eyeing metaocaml too...) On Tue, Oct 16, 2012 at 1:06 AM, wrote: > > It so happened that I had to upgrade to amd64 (Intel Core 2) last > week. I have installed FreeBSD 9.0 from scratch and OCaml 3.12.1 > from ports. I have just recompiled delimcc. All tests passed, > both for byte-code and the native compiler. > > I'm really not sure what the reported problem might be. I have used > the following line in delimcc's Makefile > OCAMLINCLUDES=./ocaml-byterun-3.11 > That OCAMLINCLUDES worked with 3.12.0 (and with 3.12.1, it seems). I'm > not sure if it works with 4.x though. > > Could you check your Makefile? Could you check that > $(LIBDIR)/Makefile.config > has sane values, where > LIBDIR := $(shell ocamlc -where) > If you have several versions of OCaml on your system, it could be that > delimcc's Makefile picks a wrong version (inconsistent with > OCAMLINCLUDES). Such an inconsistency could certainly cause a > segfault. > > > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > --f46d040716990b432504cc2e6743 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thank-you Oleg, for limiting my hunt for a red-herring. :) I only looked th= rough the web-svn changes to 3.12.1 and nothing stood out as a problematic = change... I should have installed 3.12.1 to try it out.

With 4.00.0 (and this is a new machine with no prior installs) I pulled the= corresponding files from 4.0 source into an ocaml-byterun-4.00 directory, = and the native test segfaults. Just now I tried pointing to the 3.11 direct= ory and it also segfaults. I expect going to 4.x there's been a change = of some significance for delimcc.

I'm not using GADTs or other 4.x features yet, and = delimcc is more important to me -- so I'm happy enough using 3.12 while= casually prodding at delimcc+4.x.

=A0-Tony

P.S. Thanks for the nifty gadgets! (I keep eyeing metao= caml too...)


On Tue= , Oct 16, 2012 at 1:06 AM, <oleg@okmij.org> wrote:

It so happened that I had to upgrade to amd64 (Intel Core 2) last
week. I have installed FreeBSD 9.0 from scratch and OCaml 3.12.1
from ports. I have just recompiled delimcc. All tests passed,
both for byte-code and the native compiler.

I'm really not sure what the reported problem might be. I have used
the following line in delimcc's Makefile
=A0 =A0 =A0 =A0 OCAMLINCLUDES=3D./ocaml-byterun-3.11
That OCAMLINCLUDES worked with 3.12.0 (and with 3.12.1, it seems). I'm<= br> not sure if it works with 4.x though.

Could you check your Makefile? Could you check that
=A0 =A0 =A0 =A0 $(LIBDIR)/Makefile.config
has sane values, where
=A0 =A0 =A0 =A0 LIBDIR :=3D $(shell ocamlc -where)
If you have several versions of OCaml on your system, it could be that
delimcc's Makefile picks a wrong version (inconsistent with
OCAMLINCLUDES). Such an inconsistency could certainly cause a
segfault.




--
Caml-list mailing list. =A0Subscription management and archives:
ht= tps://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs

--f46d040716990b432504cc2e6743--