Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCaml 4.03 with FLambda reports incorrect version #7304

Closed
vicuna opened this issue Jul 24, 2016 · 3 comments
Closed

OCaml 4.03 with FLambda reports incorrect version #7304

vicuna opened this issue Jul 24, 2016 · 3 comments
Assignees
Labels

Comments

@vicuna
Copy link

vicuna commented Jul 24, 2016

Original bug ID: 7304
Reporter: @mmottl
Assigned to: @gasche
Status: closed (set by @gasche on 2016-07-26T01:21:06Z)
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Monitored by: @mmottl

Bug description

The following OCaml version is reported with OCaml 4.03.0+flambda in OPAM:

ocaml --version

The OCaml toplevel, version 4.04.0+dev0-2016-02-18

This apparently causes problems with camlp4 (and dependent packages):

This version of Camlp4 is for OCaml 4.03 but you are using OCaml 4.04.0+dev0-2016-02-18.

You may want to report a version consistent with the OPAM package, possibly adding some FLambda indicator to the version information.

@vicuna
Copy link
Author

vicuna commented Jul 25, 2016

Comment author: @gasche

I'm surprised by this.

Note that to know if flambda is set or not, rather than the version information, you should look at

ocamlc -config | grep flambda

(pre-flambda versions may have no output at all)

@vicuna
Copy link
Author

vicuna commented Jul 25, 2016

Comment author: @gasche

I cannot reproduce the bug, I think that you probably had a wrong environment when testing this.

@vicuna
Copy link
Author

vicuna commented Jul 26, 2016

Comment author: @mmottl

I still don't know what exactly went wrong, possibly just a broken OPAM installation, but after having removed + reinstalled the OPAM 4.03+flambda package, it seems the problem is now solved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants