caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: Christophe Raffalli <Christophe.Raffalli@univ-savoie.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Segv while compiling ocaml-3.04
Date: Fri, 21 Dec 2001 14:01:07 +0100	[thread overview]
Message-ID: <20011221140107.A26653@pauillac.inria.fr> (raw)
In-Reply-To: <3C1DB4A6.A1B4462@univ-savoie.fr>; from Christophe.Raffalli@univ-savoie.fr on Mon, Dec 17, 2001 at 10:02:30AM +0100

Update on the gcc 2.96 issue:

A patch is now available, along with an updated source RPM and an
updated RedHat 7.2 binary RPM, all at the usual place:
        http://caml.inria.fr/ocaml/distrib.html

For those who are worried about it, the purity of the OCaml source
code isn't affected: the patch simply selects gcc compilation options
(-fomit-frame-pointer) that seem to work around the bug.

As to which versions of gcc are affected: gcc 2.96 from RH 7.2 and
Mandrake 8.1 are, I'm certain that 2.95.2 is not, and believe that 3.0
isn't either, but this has to be checked carefully.

A bug report was filed with RedHat.  (The bug was already in their
database, but I added a report for good measure.)  If someone knows
how to file a bug report for Mandrake 8.1 (which seems to be affected
as well), I can provide details.

This is actually the second time that RedHat's modified gcc breaks
OCaml.  I won't engage in RedHat bashing here, since that's rather
pointless.  We'll probably deal with this issue like we did the first
time: test the gcc version in configure and issue a strongly worded
warning, telling the users to continue at their own risks.  Just
refusing to compile for gcc 2.96 would be excessive, since apparently
not all versions of 2.96 have the bug...

- Xavier Leroy
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-12-21 13:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200112170931.KAA0000003112@beaune.inria.fr>
2001-12-17  9:02 ` Christophe Raffalli
2001-12-21 13:01   ` Xavier Leroy [this message]
2001-12-22 14:44     ` Pixel
2001-12-23  8:37       ` Xavier Leroy
2001-12-14  8:39 Christophe Raffalli
2001-12-14 13:25 ` Pixel
     [not found] ` <15385.61778.52293.648002@gargle.gargle.HOWL>
     [not found]   ` <3C1A07E9.B01890D5@univ-savoie.fr>
     [not found]     ` <15386.19382.239731.32280@hector.lesours>
2001-12-15 10:32       ` Christophe Raffalli
2001-12-20 10:50 ` Xavier Leroy
2001-12-20 11:00   ` Christophe Raffalli
2001-12-20 22:49   ` Ian Zimmerman
2001-12-21  8:22     ` Florian Hars
2001-12-21  8:28       ` Ian Zimmerman
2001-12-21  9:25       ` William Chesters
2001-12-21 10:00         ` Sven
2001-12-21  8:24     ` Luc Maranget

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=20011221140107.A26653@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=Christophe.Raffalli@univ-savoie.fr \
    --cc=caml-list@inria.fr \
    /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).