-
Notifications
You must be signed in to change notification settings - Fork 685
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
cabal-install-3.0 requires --installdir option which doesn't exist in existing ~/.cabal/configs #5973
Comments
Did you |
No, nothing told me to do so.
…Sent from my iPhone
On 30 Mar 2019, at 17.55, Francesco Gazzetta ***@***.***> wrote:
Did you cabal user-config update?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Worse than that - there's no mentioning of the config parameter |
I just experienced the same issue, and ran |
Had the same issue with |
Are you on Arch by any chance? And did you edit your |
I have the very same confusing behavior with cabal-install 3.0.1 and GHC 8.8.2. It would be nice to fix it somehow (e.g. initialize |
Alternatively, it could be nice if cabal at least informs the user that |
This change updates the `cabal install` command to use the default install directory for executables if one was not specified in either Cabal's config file or on the command line with the --installdir flag. Previously this would error out, now it warns that it used the default and continues. PR haskell#6624, resolves haskell#5973.
I ran into the same issue today on cabal 3.2.0.0, and like
Like obviously several people before me (I'm counting four more). Phadej's fix was merged after the latest current release. => Would a 3.0.0.1 release not be in order to roll out this fix for an issue which people seem to run into quite frequently? |
I ran into this issue today and found that I need to run the command again and again if I leave this bash session and come back. My scenario is that I used the system |
The text was updated successfully, but these errors were encountered: