-
Notifications
You must be signed in to change notification settings - Fork 24
installing on linux #4
Comments
Here I think that you should only have to specify opam, or did you try that unsuccessfully?
If opam is working as expected on your machine, this last line should not be needed, odd.
Likewise, if opam is working as expected, these last two lines should not be needed, odd.
I think that the
Ah, sorry, config.sh is cygwin specific and is used for non-opam installation of ocaml. Other than adding .../SLAyer/bin and .../SLAyer/tools/Z3/build to PATH, it is redundant when using opam.
This may be due to config.sh breaking opam's settings.
The slayer makefiles are not smart enough to recover from most failed Z3 builds. Manually executing
Yes, this is issue #1, the frontend could not be open-sourced, for any platform. Part of the frontend implementation is contained in Frontend.ml and frontend_esp.ml, although this code cannot currently be built as there are missing closed-source dependencies. But it could provide info on what the expected interface of the frontend is. Starting from Frontend.ml will lead to the implementation of the command-line interface. The main point is that
Yes, cygpath is specific to cygwin, and not needed elsewhere. Sorry, this is totally not clear currently.
Thanks for sharing your experience! |
Thanks for sharing. I used the following compilation process and compiled successfully without the need of removing SLAyer
|
FWIW this is the procedure I used to get SLAyer running on a freshly installed VM with
Ubuntu 14.04.1 LTS
.I started with the following per the ocaml website:
camlidl
seems to hardcode/usr/local/lib/ocaml
in theconfigure/Makefile
.Then followed did the following:
I seemed to need to modify a Makefile,
~/SLAyer/tools/Z3/build/api/ml/Makefile
to:CAMLIDL=-I/home/joe/.opam/4.02.3/lib/camlidl
rather than the path fromocamlc -where
.This failed, I then had to remove the repo and try again, afterwards it then complied fully. I assume this is something getting screwed up in the ENV or various library paths during the initial install attempt that restarting from scratch seems to fix. Unfortunately I am not sure what it is.
From there slayer runs but exits quietly but with an exit code of 1.
strace -f
shows that this is due to nothing calledfrontend
on the path. Which #1 seems to be about.For the heck of it I created a
frontend
file:Which tells me it's trying to run
frontend $MYCFILENAME -fe_norm true
. Seems like without some sort of special frontend client it's not very usable on linux at least.Also possibly worth noting,
cygpath
isn't installed:Also, best I can tell something like
cp /home/joe/SLAyer/src/../tools/Z3/build/api/ml/* /home/joe/.opam/4.02.3/lib/ocaml/
doesn't seem to help.Thanks for open sourcing this project. Hope this helps others!
The text was updated successfully, but these errors were encountered: