-
Notifications
You must be signed in to change notification settings - Fork 701
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
Unix-style /mingw64/...
paths not understood
#9479
Comments
mingw64
paths not understood/mingw64/...
paths not understood
@mpickering, @bgamari: any comment from the GHC side? |
It seems this is triggered by code in |
I don't understand exactly what you are doing. Are you hardcoding |
Pkgconf packages write it that way, most if not all of them:
I'm not hardcoding it in my config (which in any case should still work). 142 out of 144 pkgconf files I have in my machine use this terminology:
And I did not manipulate those. They come from installing stuff via MinGW's |
Are you using pkgconf or mingw-w64-pkgconf? |
I'm using |
msys2/MINGW-packages#6958 suggests this is a bug in the respective packages (in this case termcap?). |
Wait a second: $ rg "\-I/mingw"
tre.pc
10:Cflags: -I${includedir} -D_FORTIFY_SOURCE=2 -D__USE_MINGW_ANSI_STDIO=1 -I/mingw64/include
libwmf.pc
10:Cflags: -I/mingw64/include/freetype2 -I/mingw64/include/libpng16 -I/mingw64/include/harfbuzz -I/mingw64/include/glib-2.0 -I/mingw64/lib/glib-2.0/include
isl.pc
18:Cflags: -I${includedir} -I/mingw64/include
ddjvuapi.pc
13:Cflags: -I/mingw64/include
$ PKG_CONFIG_SYSTEM_INCLUDE_PATH=1 pkgconf --cflags-only-I tre
-IC:/msys64/mingw64/include -I/mingw64/include Did I just by luck (I selected a couple of packages randomly) hit one of the 4 packages that define include directories hardcoded in the |
Ah, if I manually remove that |
Please report those issues upstream. |
Reported upstream:
|
I discussed on MSYS2's Discord server what should be done in this case. The conclusion for these cases seems to be:
So these issues should maybe not be reported to the upstream library but instead a patch to Thoughts @hasufell ? Footnotes |
Sure |
In MinGW,
pkgconf
(at least 2.1.0) offers/mingw64/include
as aninclude-dirs
. This is rejected by saying the following:I'm unsure whether this is a Cabal bug or a GHC (or for that matter ghc-pkg) bug, but perhaps Cabal can fix it? There should be some way of normalizing that path. Note that the path exists:
This seems to be a recurrent issue, which is due to the specification in the
.pc
file:To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should understand either
/mingw64/include
asC:\msys64\mingw64\include
System information
cabal
HEAD (but any would do)ghc
9.6.3The text was updated successfully, but these errors were encountered: