From: Anthony Tavener <anthony.tavener@gmail.com>
To: oleg@okmij.org
Cc: christophe.raffalli@univ-savoie.fr, caml-list@inria.fr
Subject: Re: [Caml-list] Re: ocaml 3.12.1 and delimcc
Date: Tue, 16 Oct 2012 08:59:36 -0600 [thread overview]
Message-ID: <CAN=ouMQXqRGQAjXMA=tP8EhEDuOTs5=ZNtL9zUF1vcqAUrnTHQ@mail.gmail.com> (raw)
In-Reply-To: <20121016070618.80750.qmail@www1.g3.pair.com>
[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]
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, <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
> 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
>
[-- Attachment #2: Type: text/html, Size: 2716 bytes --]
next prev parent reply other threads:[~2012-10-16 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 7:06 oleg
2012-10-16 14:59 ` Anthony Tavener [this message]
2012-10-19 2:20 ` oleg
2012-10-19 10:35 ` Gabriel Kerneis
2012-10-20 17:25 ` Anthony Tavener
2012-10-26 3:47 ` Anthony Tavener
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='CAN=ouMQXqRGQAjXMA=tP8EhEDuOTs5=ZNtL9zUF1vcqAUrnTHQ@mail.gmail.com' \
--to=anthony.tavener@gmail.com \
--cc=caml-list@inria.fr \
--cc=christophe.raffalli@univ-savoie.fr \
--cc=oleg@okmij.org \
/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).