From: Julia Lawall <julia.lawall@lip6.fr>
To: Oliver Schwahn <schwahn@cs.tu-darmstadt.de>
Cc: cocci@systeme.lip6.fr
Subject: Re: [Cocci] Build issue after stdcompat upgrade
Date: Mon, 10 Dec 2018 17:13:05 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1812101711320.3486@hadrien> (raw)
In-Reply-To: <9957435e-f4bc-92aa-0a9e-295c0d77345b@cs.tu-darmstadt.de>
On Mon, 10 Dec 2018, Oliver Schwahn wrote:
> > > Do you have any suggestion for a workaround?
> >
> > Can you upgrade to 4.06? I also have this problem with 4.05.
>
> Thanks for the suggestion. OCaml 4.05 was indeed the problem. I upgraded to
> 4.07 and that worked fine.
> I also had the chance to check on configurations with OCaml 4.01.0 and 4.02.3,
> which also work as expected.
>
> Just out of curiosity, when I run the included tests with:
> ./spatch.opt --testall
> I get a score of: good = 529/552.
> Is that the expected outcome or is something not working correctly?
Yes, it is the expected outcome. The tests should only depend on OCaml
features so should be portable, and really only exist for the developers.
The tests that fail are things that should work but don't.
julia
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2018-12-10 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 14:29 [Cocci] Build issue after stdcompat upgrade Oliver Schwahn
2018-12-10 14:55 ` Julia Lawall
2018-12-10 15:42 ` Oliver Schwahn
2018-12-10 16:13 ` Julia Lawall [this message]
2018-12-10 17:42 ` Himanshu Jha
2018-12-13 18:06 ` Flykt, Patrik
2018-12-13 18:32 ` Himanshu Jha
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=alpine.DEB.2.20.1812101711320.3486@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=schwahn@cs.tu-darmstadt.de \
/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).