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

On Windows cabal seems to search for unsuffixed binaries only #5936

Closed
Mistuke opened this issue Mar 13, 2019 · 5 comments
Closed

On Windows cabal seems to search for unsuffixed binaries only #5936

Mistuke opened this issue Mar 13, 2019 · 5 comments

Comments

@Mistuke
Copy link
Collaborator

Mistuke commented Mar 13, 2019

I have noticed that cabal has trouble finding e.g. pkg-config because it's looking for pkg-config instead of pkg-config.exe.

The search for binary functionality on Windows needs to search for both, giving preference to .exe as that's likely to be found.

I do remember this used to work before.

@hvr
Copy link
Member

hvr commented Mar 13, 2019

Did you experience this with a version of cabal that had #5753 in it (and note that no released version of cabal currently has this)?

@Mistuke
Copy link
Collaborator Author

Mistuke commented Mar 13, 2019

yeah, it's one of the latest head builds. AppVeyor should show it by putting it in verbose mode. One sec let me check the latest head.

@hvr
Copy link
Member

hvr commented Mar 13, 2019

@Mistuke is there any way you could help debug this? I.e. is it findProgramOnSearchPath that fails to find pkg-config or is it some other codepath being at fault here?

@Mistuke
Copy link
Collaborator Author

Mistuke commented Mar 13, 2019

Sure, I've started a build to check. (not on my usual machine so don't have one handy).

@Mistuke
Copy link
Collaborator Author

Mistuke commented Mar 13, 2019

hmm that's interesting, it seems to work on the latest head..

Using pkg-config version 0.29.2 found on system at:
C:\dev\msys64\mingw64\bin\pkg-config.exe

I will have to wait till I'm home to find the other build I was trying. But this seems to not be an issue anymore... Sorry for the noise.

@Mistuke Mistuke closed this as completed Mar 13, 2019
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

2 participants