From: Florian Angeletti <florian.angeletti@inria.fr>
To: caml-list@inria.fr
Subject: [Caml-list] OCaml 4.10.0, first beta
Date: Fri, 10 Jan 2020 19:36:39 +0100 [thread overview]
Message-ID: <0609233a-ca50-c444-7347-1ab29fce15da@inria.fr> (raw)
Dear OCaml users,
The release of OCaml 4.10.0 is approaching. We have created
a first beta version to help you adapt your software to the new features
ahead of the release.
During our preliminary tests for this new beta, we discovered that the
recent
work towards a multicore-ready OCaml runtime introduced compatibility issues
within some opam packages, that were tweaking the runtime internals.
Most of those opam packages have been fixed, or will be soon.
Nevertheless, if you are affected by such compatibility issue, please
speak up.
The source code is available at these addresses:
https://github.com/ocaml/ocaml/archive/4.10.0+beta1.tar.gz
https://caml.inria.fr/pub/distrib/ocaml-4.10/4.10.0+beta1.tar.gz
The compiler can also be installed as an OPAM switch with one of the
following commands.
opam switch create ocaml-variants.4.10.0+beta1
--repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
or
opam switch create ocaml-variants.4.10.0+beta1+<VARIANT>
--repositories=default,beta=git+https://github.com/ocaml/ocaml-beta-repository.git
where you replace <VARIANT> with one of these:
afl
flambda
fp
fp+flambda
We want to know about all bugs. Please report them here:
https://github.com/ocaml/ocaml/issues
Happy hacking,
-- Florian Angeletti, for the OCaml team.
next reply other threads:[~2020-01-10 18:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 18:36 Florian Angeletti [this message]
2020-01-28 9:46 ` [Caml-list] OCaml 4.10.0, second beta Florian Angeletti
2020-02-07 9:01 ` [Caml-list] OCaml 4.10.0, first release candidate Florian Angeletti
2020-02-12 9:35 ` [Caml-list] OCaml 4.10.0, second " Florian Angeletti
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=0609233a-ca50-c444-7347-1ab29fce15da@inria.fr \
--to=florian.angeletti@inria.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).