caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Alexander V. Voinov" <avv@quasar.ipa.nw.ru>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Bugfix for ocaml-3.05 problem (was: recompiling ocamlnet  & PXP with 3.05)
Date: Tue, 30 Jul 2002 20:44:11 -0700	[thread overview]
Message-ID: <3D475D0B.2904444A@quasar.ipa.nw.ru> (raw)
In-Reply-To: <20020730211821.GA1806@ice.gerd-stolpmann.de>

Hi Gerd,

It helped with the first part of the problem below (on Linux). But under
Solaris it still crashes at:

ocamlfind ocamlc -g  -package "unix pcre" -thread -c netstring_pcre.mli

Unfortunately this moment I can't spend enough time to trace it within
the compiler.

Alexander

Gerd Stolpmann wrote:
> 
> On 2002.07.30 21:01 Alexander V.Voinov wrote:
> > Hi
> >
> > ocamlc crashes at some of the sources of the mentioned modules.
> >
> > Under Linux/x86 it crashed on
> >
> > ocamlfind ocamlc -g  -package "netstring" -c pxp_document.ml
> > ocamlc got signal and exited
> >
> > Under Solaris/Sparc it crashed on the netstring as well. Netstring
> > (and PXP) compiled OK in the same environment under 3.04.
> 
> Hi,
> 
> yesterday I already got a similar report from Michaël Marchegay, and
> I could reproduce the problem. I submitted a bug report (23:44),
> and Xavier Leroy and Damien Doligez fixed the problem until 15:36.
> Really phantastic response time!
> 
> You can read the bug report with some more details how to
> circumvent the problem:
> 
> http://caml.inria.fr/bin/caml-bugs/fixed?id=1273;page=44;user=guest
> 
> For your convenience, I have the attached the patch. Apply it
> as follows:
> 
> cd ocaml-3.05/byterun
> patch -p0 <../../whereever-your-patch-is/patch
> 
> Then rebuild the whole system:
> 
> cd ..
> make clean
> make world opt opt.opt
> 
> It would be sufficient to rebuild ocamlrun and all statically linked
> binaries, there is no change in the libraries (except libcamlrun.a),
> but I don't know how to do this.
> 
> I think O'Caml-3.05 is still worth to be tried, there are numerous
> improvements, and at least for me this GC bug does not prevent me
> from using this version. It is not a fundamental problem, only a
> single error.
> 
> Gerd
> --
> ----------------------------------------------------------------------------
> Gerd Stolpmann      Telefon: +49 6151 997705 (privat)
> Viktoriastr. 45
> 64293 Darmstadt     EMail:   gerd@gerd-stolpmann.de
> Germany
> ----------------------------------------------------------------------------
> 
>   ------------------------------------------------------------------------
> 
>    ocaml-3.05-gc.patchName: ocaml-3.05-gc.patch
>                       Type: Plain Text (text/plain)
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2002-07-31  3:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30 19:01 [Caml-list] recompiling ocamlnet & PXP with 3.05 Alexander V.Voinov
2002-07-30 21:18 ` [Caml-list] Bugfix for ocaml-3.05 problem (was: recompiling ocamlnet & PXP with 3.05) Gerd Stolpmann
2002-07-31  3:44   ` Alexander V. Voinov [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=3D475D0B.2904444A@quasar.ipa.nw.ru \
    --to=avv@quasar.ipa.nw.ru \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    /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).