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

Cannot find prelude when running from same directory as binary distribution executable #113

Closed
acfoltzer opened this issue Sep 23, 2014 · 1 comment
Assignees
Labels
bug Something not working correctly
Milestone

Comments

@acfoltzer
Copy link
Contributor

If one invokes cryptol directly from the directory where the executable is located, it will not be able to find the Cryptol prelude.

This only seems to affect binary distributions; in-place binaries in the cabal sandbox seem to have no trouble.

@acfoltzer acfoltzer added the bug Something not working correctly label Sep 23, 2014
@acfoltzer acfoltzer self-assigned this Sep 23, 2014
@acfoltzer acfoltzer added this to the Cryptol 2.1 milestone Sep 23, 2014
@acfoltzer
Copy link
Contributor Author

This is now totally broken for Windows builds. It works on the Jenkins slaves because of the fallback to the cabal-install-specified location, but does not work in a distribution. This will delay the 2.1 release.

@acfoltzer acfoltzer reopened this Oct 4, 2014
acfoltzer added a commit that referenced this issue Oct 14, 2014
This "fix" adds two locations to the search path for Cryptol modules so that we can find the prelude on both Windows and Unix platforms. This is not ideal and should be replaced in the next version, but should have no negative impact for now unless people have multiple Cryptol.cry files hanging out in their filesystems.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something not working correctly
Projects
None yet
Development

No branches or pull requests

1 participant