-
Notifications
You must be signed in to change notification settings - Fork 704
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 new-build fails on time library #5223
Comments
Hmm, this looks like #5169 but in this |
I'm reopening this, as this one's different enough from #5169, insofar as I consider this one a fixable issue; quoting #5169 (comment)
This was pointed out by @phadej as well here; so what we could do is have Cabal look also in the autogen folder for (relative) folders explicitly specified as @angerman what do you think? |
@hvr guess that could work. I'm a bit weary if we end up looking for headers just all over the place. I'm not sure if we could (or even should) try to enforce a better system for generated files. |
This also prevents libraries like
|
This seems like something we should try to sort out before new-style commands become the default. cc @typedrat. |
@RyanGlScott does this only occur when I.e. this doesn't appear to be an issue for non-inplace cases as in e.g.
|
@hvr, correct. I only experienced these errors when trying to get these packages in-place. The original context in which I discovered this bug was haskell/deepseq#39, where I needed to build |
It seems, I got the same problem when building I've put all its dependencies, including
The |
This still happens for local Which means that we cannot even consider using |
|
My PR fixes the original However,
The
so it should be
|
I'm not sure if it's related but I seem to possibly running into this issue as well. I'm not sure what I could do to investigate further.. Essentially I have a cabal dependency on
|
I noticed this when debugging haskell/deepseq#39. To reproduce:
On the other hand,
cabal build
works without issue. This is because the generatedHsTimeConfig.h
file seems to be put in a place wherecabal
can't find it:The text was updated successfully, but these errors were encountered: