From: Anil Madhavapeddy <anil@recoil.org>
To: Hannes Mehnert <hannes@mehnert.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml release 4.04.2
Date: Fri, 23 Jun 2017 22:18:12 +0100 [thread overview]
Message-ID: <D5F4DBA1-C4AA-4784-865E-9AC965D59A19@recoil.org> (raw)
In-Reply-To: <488d68db-1c76-de6a-0722-e503a76cf656@mehnert.org>
On 23 Jun 2017, at 21:38, Hannes Mehnert <hannes@mehnert.org> wrote:
>
> Damien,
>
> thank you for your work on the release.
>
> On 23/06/2017 16:18, Damien Doligez wrote:
>> Workarounds:
>> - Upgrade to OCaml 4.04.2 or higher.
>> or - Compile the OCaml distribution with the "-no-cplugins" configure option.
>> or - OPAM users can "opam update && opam switch recompile 4.04.1", as
>> the repository has had backported patches applied.
>
> I fail to find any 4.04.1 backports in the opam repository at
> https://github.com/ocaml/opam-repository/tree/master/compilers/4.04.1
>
> Thus, the only way is to upgrade to 4.04.2 (or downgrade to 4.03).
Sorry, the opam backports are lagging as the final patch in 4.04.2 changed
a little bit. However, the upgrade to 4.04.2 should have zero side effects
in practise for a source installation via OPAM, so please do let me know
if you run into any difficulty upgrading from 4.04.0/1 to 4.04.2.
TL;DR do `opam update && opam switch 4.04.2` for now.
regards,
Anil
prev parent reply other threads:[~2017-06-23 21:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 15:18 Damien Doligez
2017-06-23 16:47 ` Alexey Egorov
2017-06-23 19:05 ` David Allsopp
2017-06-23 19:13 ` Gabriel Scherer
2017-06-23 19:53 ` octachron
2017-06-23 20:38 ` Hannes Mehnert
2017-06-23 21:18 ` Anil Madhavapeddy [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=D5F4DBA1-C4AA-4784-865E-9AC965D59A19@recoil.org \
--to=anil@recoil.org \
--cc=caml-list@inria.fr \
--cc=hannes@mehnert.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).