Skip to content

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

Open
@fgaz

Description

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

Activity

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

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions