Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Fabrice Le Fessant <Fabrice.Le_fessant@inria.fr>
To: Damien Doligez <damien.doligez@inria.fr>,
	caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.04.0+beta1
Date: Fri, 12 Aug 2016 10:09:03 +0000	[thread overview]
Message-ID: <CAHvkLrOM-7O+gC-97xcR+r82+9=CfK9p87xFEYk+sTR8AHvEvA@mail.gmail.com> (raw)
In-Reply-To: <3F86857B-79DC-4FCE-8727-691C23120C3F@inria.fr>

[-- Attachment #1: Type: text/plain, Size: 1319 bytes --]

Hi,

  I started a branch on opam-builder for 4.04.0+beta1, which is now
displayed in the matrix:

http://opam.ocamlpro.com/builder/

  The logs of compilation are available online, for packages that fail to
compile with 4.04.0+beta1. Note that there is a known issue in 4.04.0+beta1
with C libraries put directly on the command line during linking (instead
of using `-cclib`), that make `omake` fail. The issue is solved in the next
beta.

Enjoy !
--Fabrice

On Tue, Aug 9, 2016 at 4:34 PM Damien Doligez <damien.doligez@inria.fr>
wrote:

> Dear OCaml users,
>
> The release of OCaml 4.04.0 will take place in September. We have created
> a beta version to help you adapt your software to the new features ahead of
> the release.
>
> The source code is available at this address:
>
>   http://caml.inria.fr/pub/distrib/ocaml-4.03/
>
> and the compiler will soon be available as the "4.04.0+beta1" OPAM switch.
>
> We want to know about all bugs. Please report them here:
>   http://caml.inria.fr/mantis/bug_report_page.php
>
> Happy hacking,
>
> -- Damien Doligez for the OCaml team.
>
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs

[-- Attachment #2: Type: text/html, Size: 2245 bytes --]

      parent reply	other threads:[~2016-08-12 10:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 13:15 Damien Doligez
2016-08-09 14:24 ` Goswin von Brederlow
2016-08-11 15:10   ` Damien Doligez
2016-08-11 16:28     ` David Allsopp
2016-08-12 10:47       ` Damien Doligez
2016-08-12 10:58         ` Fabrice Le Fessant
2016-08-12 12:09           ` Damien Doligez
2016-08-12 12:23             ` Daniel Bünzli
2016-08-12 12:25             ` Grégoire Henry
2016-08-12 12:50               ` David Allsopp
2016-08-16 12:37                 ` Damien Doligez
2016-08-16 12:44                   ` Gabriel Scherer
2016-08-16 12:54                   ` David Allsopp
2016-08-26 14:00                     ` Louis Gesbert
2016-09-05  9:24                       ` Goswin von Brederlow
2016-08-12 12:46         ` David Allsopp
2016-08-12 14:56     ` [Caml-list] Debian's version-numbering convention Hendrik Boom
2016-08-12 15:57       ` David Allsopp
2016-08-12 16:06         ` Hendrik Boom
2016-08-09 16:06 ` [Caml-list] OCaml 4.04.0+beta1 Mohamed Iguernlala
2016-08-10 16:42   ` Mohamed Iguernlala
2016-08-10 16:46   ` Anil Madhavapeddy
2016-08-12 10:09 ` Fabrice Le Fessant [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='CAHvkLrOM-7O+gC-97xcR+r82+9=CfK9p87xFEYk+sTR8AHvEvA@mail.gmail.com' \
    --to=fabrice.le_fessant@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=damien.doligez@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