caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <xavier.leroy@inria.fr>
To: luther@dpt-info.u-strasbg.fr
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: 3.05 and future 3.06 binary compatibility ?
Date: Thu, 1 Aug 2002 14:09:39 +0200	[thread overview]
Message-ID: <20020801140939.A6160@pauillac.inria.fr> (raw)
In-Reply-To: <20020801093701.GA20892@iliana>; from root@iliana on Thu, Aug 01, 2002 at 11:37:01AM +0200

> Will this 3.06 release be compatible with 3.05, or will we have to
> rebuild all the libraries that were built with 3.05 for 3.06 ?
> 
> I know you strongly recommend that libraries are rebuilt for each new
> ocaml version, but a parsing bug hardly seem to affect binary
> compatibility.

It's a type-checking bug, not a parsing bug.  You're correct that
fixing it is likely not to break binary compatibility.  

However, I have bad news for you: it turns out that the .cmi files for
3.05 have a different format than those for 3.04, and we forgot to
change the magic number in .cmi files whose purpose is precisely to
guard against using a .cmi file in an old format.  (The segfault
reported by Alexander Voinov on this list was tracked down to such an
undetected use of an old .cmi file.)  Hence, the magic number will be
bumped in 3.06, causing 3.05-compiled files to be rejected.

I know you will hate me for this, but I really don't see any better
solution.

- Xavier Leroy, who also spent a while rebuilding all his libs

PS.  Your mail had an invalid From address "root@iliana".  






> 
> Friendly,
> 
> Sven Luther
-------------------
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-08-01 12:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-29 12:45 [Caml-list] OCaml 3.05 released Xavier Leroy
2002-07-29 14:36 ` Nicolas Cannasse
2002-07-30  0:46 ` Shawn Wagner
2002-07-30  3:50 ` Scott J.
2002-07-30  7:34   ` John Prevost
2002-07-30  7:46   ` [Caml-list] Serious typechecking error involving new polymorphism (crash) John Prevost
2002-07-30  7:58     ` Xavier Leroy
2002-07-30  8:22       ` John Prevost
2002-07-30  8:47         ` Xavier Leroy
2002-07-30  8:37       ` Sven LUTHER
2002-07-30 14:11         ` [Caml-list] bug-fix branches Xavier Leroy
2002-07-30 16:15           ` Sven LUTHER
2002-08-01  9:37           ` [Caml-list] 3.05 and future 3.06 binary compatibility ? root
2002-08-01 12:09             ` Xavier Leroy [this message]
2002-08-01 15:56               ` [Caml-list] " Sven LUTHER
2002-08-08  8:37               ` Sven LUTHER
2002-08-09 12:25                 ` Xavier Leroy
2002-08-09 13:16                   ` Sven LUTHER
2002-07-30  7:51   ` [Caml-list] OCaml 3.05 released Dmitry Bely
2002-07-30 15:01     ` Scott J.
2002-07-30 15:11       ` Dmitry Bely
2002-08-02  5:31   ` Jacques Garrigue
2002-08-02 11:15     ` Tim Freeman
2002-07-30  7:48 ` [Caml-list] Record with one non mutable filed Christophe Raffalli
2002-07-30 11:49 ` [Caml-list] OCaml 3.05 released Yaron M. Minsky

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=20020801140939.A6160@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=luther@dpt-info.u-strasbg.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).