From: "Richard W.M. Jones" <rich@annexia.org>
To: Gabriel Scherer <gabriel.scherer@inria.fr>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml 4.07.0+rc1
Date: Wed, 20 Jun 2018 14:30:51 +0100 [thread overview]
Message-ID: <20180620133051.kb7oa5osyqq2kzp6@annexia.org> (raw)
In-Reply-To: <CAPFanBHgAtdFG90rK=6sdWMVhC06NgQU6XM11Lf3BgakEAwxCg@mail.gmail.com>
On Tue, Jun 19, 2018 at 05:51:32PM +0200, Gabriel Scherer wrote:
> Dear OCaml users,
>
> The release of OCaml version 4.07.0 is imminent. We have created
> a release candidate for your testing pleasure. Please download
> the sources, compile, install, and test your favourite software
> with it, and let us know whether it works for you.
>
> We want to know about any show-stopping bugs, especially
> in the compilation and installation phases.
>
> This release candidate is available as an opam switch 4.07.0+rc1,
> and as source archive at this address:
> https://caml.inria.fr/pub/distrib/ocaml-4.07/
>
> Happy hacking,
I'm not sure if this is a bug in the compiler, or something which just
happened to work before, but it seems like the OCaml compiler now
fails to parse / ignore '# <nnn>' line number directives left in the
source after running tools like cppo. This stops extlib from
compiling.
As far as I recall, 4.07.0+beta2 did not have this problem, assuming
it is a problem.
I've worked around it in extlib by using the 'cppo -n' option.
Rich.
--
Richard Jones
--
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
next prev parent reply other threads:[~2018-06-20 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-19 15:51 Gabriel Scherer
2018-06-20 13:30 ` Richard W.M. Jones [this message]
2018-06-20 13:34 ` Nicolás Ojeda Bär
2018-06-20 13:36 ` Richard W.M. Jones
2018-06-20 13:44 ` Richard W.M. Jones
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=20180620133051.kb7oa5osyqq2kzp6@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@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).