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

cabal init -n fails when cabal is not in $PATH #9687

Open
fgaz opened this issue Feb 2, 2024 · 0 comments
Open

cabal init -n fails when cabal is not in $PATH #9687

fgaz opened this issue Feb 2, 2024 · 0 comments

Comments

@fgaz
Copy link
Member

fgaz commented Feb 2, 2024

Describe the bug

cabal init -n fails when cabal is not in $PATH. seems like it wants to call itself?

cabal: readCreateProcessWithExitCode: posix_spawnp: does not exist (No such file or directory)

To Reproduce
Steps to reproduce the behavior:

Ensure cabal is not in $PATH

$ mkdir mypackage
$ cd mypackage
$ /path/to/cabal init -n

Expected behavior

The package is initialized

System information

Additional context

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant