-
Notifications
You must be signed in to change notification settings - Fork 81
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
How to bring up a REPL? #742
Comments
Your latter command session works for me on Linux. Perhaps this is a Darwin specific problem. @judah seen this before? |
The latter command failed for me with bazel-0.16.2 on Mac OS High Sierra, though with a different error:
|
@mboes does it work for you even after a "clean"?
Do you get similar output, or do you get the "lib" outputs still built from the repl too on Linux? |
@judah same behaviour as you. |
There seem to be two bugs here. I do likewise get the same output as @philderbeast's second command session in the description. |
That should be fixed once we switch the repl code to runfiles (#348). |
We suffix all the build directories and files that we make with a package name and version. As package name is a target name, there can only be a unique one in single project and we preserve some sanity in build environment, at least for the directories we declare and pass around. This allows multiple `haskell_library` and `haskell_binary` targets in a single package. Closes #7.
@Profpatsch ok so is there anything left here to do that isn't a dupe of #348? |
Actually all of that should be fixed by #736, according to Andreas. |
Please show how to bring up a REPL in the tutorial. From #380 it looks like I might be able to run a
-repl
target to do this.The command to run as shown now in the readme;
From the root folder, trying to run the
-repl
target;From the tutorial folder, trying to run the
-repl
target;The text was updated successfully, but these errors were encountered: