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

When ghc is not in path, clash won't run (with horrible error message) #104

Closed
ggreif opened this issue Dec 18, 2015 · 1 comment
Closed

Comments

@ggreif
Copy link
Contributor

ggreif commented Dec 18, 2015

Issue #82 describes a problem where clash queried the "wrong" GHC. This time it would query the right one, but (if) it is not in path, so it fails with

fd:5: hGetLine: end of file

This is a rather low-prio bug, I just handed over a full pathname to clash to another colleague and he could not start it. Turned out that he had to add my ~/bin to his path.

Catching this error and issuing a nice error message along the lines of Could not invoke the GHC compiler that CLaSH was built with. Make sure it is in your $PATH would be a big plus.

@christiaanb
Copy link
Member

You should now get:

~/devel/clash-compiler(master *) $ ./clash-ghc/.stack-work/dist/x86_64-linux/Cabal-1.22.4.0/build/clash/clash --interactive
CLaSH needs the GHC compiler it was build with, ghc-7.10.2, but it was not found. Make sure its location is in your PATH variable.

christiaanb pushed a commit that referenced this issue Sep 6, 2018
This uses a lazy pattern to delay deconstruction of the enable signal
until after the current value has been yielded.

Fixes #104
leonschoorl pushed a commit that referenced this issue Jul 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants