-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Z3 build scripts assume there's a single ocamlfind path location #5814
Comments
Are you going to add a pull request or asking for more input? |
If you're ok with my analysis feel free to go ahead and commit the patch :-). |
@k4rtik - what do you think about the patch from this sketchy character? |
I think we are really calling in @arbipher here to look at this. See #5617 where these changes were last made. But since I already spent some time looking at it, how would we know that the last entry is the correct entry for stublibs? The patch needs to be made more resilient or the right path determined without reliance on |
I agree this may cause problems. I didn't notice My previous fix uses the path to find
The conf file can be found by $ cat /home/exx/.opam/4.13.1/lib/findlib.conf
destdir="/home/exx/.opam/4.13.1/lib"
path="/home/exx/.opam/4.13.1/lib"
ocamlc="ocamlc.opt" I am thinking since Then the patch will be this at the line
|
Perfect, |
Thanks for the improved solution -- best not to trust patches from sketchy characters indeed! |
lol, as the current maintainer of the z3-ocaml on opam, I know two faces in the photo! |
This assumes the output of
ocamlfind printconf path
is a single entry:z3/scripts/mk_util.py
Line 1998 in 4749495
This is incorrect: the user may export OCAMLPATH to inform ocamlfind that there are multiple directories in which to find packages. For instance, on my machine:
This generates an incorrect
ocamlmklib
invocation:which in turn makes the build fail:
Proposed patch:
Thanks,
Jonathan
The text was updated successfully, but these errors were encountered: