|Anonymous | Login | Signup for a new account||2019-02-21 12:03 CET|
|Main | My View | View Issues | Change Log | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002391||Frama-C||Kernel > Makefile||public||2018-07-25 12:49||2018-09-05 16:28|
|Status||closed||Resolution||unable to reproduce|
|Platform||x64||OS||Ubuntu Linux||OS Version||16.04|
|Product Version||Frama-C GIT, precise the release id|
|Target Version||Fixed in Version|
|Summary||0002391: Can't compile|
|Description||Got this file: https://frama-c.com/download/frama-c-Chlorine-20180502.tar.gz [^]|
Unpacked, typed "./configure", then "make" and got:
File "src/libraries/stdlib/integer.mli", line 26, characters 9-12:
Error: Unbound module Z
share/Makefile.generic:70: recipe for target 'src/libraries/stdlib/integer.cmi' failed
make: *** [src/libraries/stdlib/integer.cmi] Error 2
|Tags||No tags attached.|
|Attached Files|| make_stdout [^] (3,517 bytes) 2018-07-25 16:04 [Show Content]
make_stderr [^] (144 bytes) 2018-07-25 16:04 [Show Content]
config.log [^] (28,188 bytes) 2018-07-25 16:04
Have you installed the Zarith OCaml library as mentioned in the installation instructions?
If yes, then could you please attach the content of the config.log file generated by configure, as well as the result of running VERBOSEMAKE=yes make, that will give the exact invocation of the OCaml compiler?
Yes, I've installed:
dennis@bigbox ~ % opam install zarith
[NOTE] Package zarith is already installed (current version is 1.7).
I'll try to upload the files now.
Thanks. I don't see anything wrong in your logs, and I'm not able to reproduce the issue. One possibility would be that opam is in an incoherent state: What do the following two commands show?
opam switch show
ocamlfind -query zarith
Given your config.log, the former should output "system" and the latter something like ...../system/zarith. If there is a discrepancy, you should probably run eval $(opam config env) and make sure that all packages needed by Frama-C (ocamlgraph zarith ocamlfind) are installed in the current switch.
If everything seems fine, check that there is a z.cmi file in the install directory of zarith ad reported by ocamlfind. If not, the installation of zarith is broken, and you should try to reinstall it.
If again everything seems fine at this level, I'm afraid I won't be able to suggest much more than using opam to install Frama-C as well. Note that if you want to keep the build directory used by opam (hence the sources of Frama-C), you can use opam install -b frama-c
dennis@bigbox ~ % opam switch show
dennis@bigbox ~ % ocamlfind -query zarith
What do you mean by "eval $(opam config env)"? Should I run this in bash?
I've installed frama-c from opam successfully, but opam has previous version (2017), this is why I tried to build from source tree :)
> What do you mean by "eval $(opam config env)"? Should I run this in bash?
Yes, whenever you do opam switch SWITCH_NAME, you have to run the above command to ensure that opam and your shell have the same idea of what is the current version (switch in opam's parlance) of OCaml to be used. But in your case, I'd tend to think that everything is fine.
> I've installed frama-c from opam successfully, but opam has previous version (2017), this is why I tried to build from source tree :)
Have you run opam update or pinned frama-c to a specific version? the latest version of the package in opam is 20180502 and this is what you should get by default. There might however be dependencies issues that prevent opam from installing this version, e.g if 20170501 was installed, you might want to remove frama-c-base and install a fresh frama-c. In any case, you can use "opam install frama-c 20180502" to specify that you want this version of Frama-C and not an older one.
|Yes, now I can install latest from opam. Thanks a lot! This what I wanted...|
|I'm glad that it worked in the end. I'm marking the bug as resolved/cannot reproduce, as I feel the original issue with the absence of the Z module of zarith is more likely a local opam installation problem and can't really be investigated remotely.|
|2018-07-25 12:49||yurichev||New Issue|
|2018-07-25 12:49||yurichev||Status||new => assigned|
|2018-07-25 12:49||yurichev||Assigned To||=> bobot|
|2018-07-25 15:49||virgile||Note Added: 0006618|
|2018-07-25 16:04||yurichev||Note Added: 0006619|
|2018-07-25 16:04||yurichev||File Added: make_stdout|
|2018-07-25 16:04||yurichev||File Added: make_stderr|
|2018-07-25 16:04||yurichev||File Added: config.log|
|2018-07-25 18:00||virgile||Note Added: 0006621|
|2018-07-26 02:39||yurichev||Note Added: 0006622|
|2018-07-26 09:07||virgile||Note Added: 0006623|
|2018-07-26 12:46||yurichev||Note Added: 0006624|
|2018-07-26 13:52||virgile||Note Added: 0006625|
|2018-07-26 13:52||virgile||Status||assigned => resolved|
|2018-07-26 13:52||virgile||Resolution||open => unable to reproduce|
|2018-07-26 13:52||virgile||Assigned To||bobot => virgile|
|2018-09-05 16:28||signoles||Status||resolved => closed|
|Copyright © 2000 - 2019 MantisBT Team|