-
Notifications
You must be signed in to change notification settings - Fork 712
fix(Cabal-syntax): Remove left-over file after #8980 #9198
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @andreabedini
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please feel free to set the merge_me label.
4c5d8a9
to
fef3bb9
Compare
It seems this change breaks GHC bootstrapping process: https://gitlab.haskell.org/ghc/ghc/-/jobs/1665720#L5755 Without Relevant part of https://gitlab.haskell.org/ghc/ghc/-/blob/master/.gitlab-ci.yml#L691: # Bootstrapping should not depend on HAPPY or ALEX so set them to false
# so the build fails if they are invoked.
- export HAPPY=/bin/false; export ALEX=/bin/false Could |
Just restoring |
@Bodigrim I will look into this tomorrow about whether we need to patch hadrian to resolve this. |
I believe @hamishmack had run into this issue with Hadrian already and make a fix in Haskell.nix. |
I only made a branch of GHC that bumped the Cabal submodule to a version with this PR. https://gitlab.haskell.org/hamishmack/ghc/-/tree/hkm/bump-Cabal |
@Bodigrim @mpickering Is the quoted comment still applicable/relevant? I admit that I don't have much experience with boostrapping or cross-compiling but I ask because just before that we bootstrap hadrian:
and, in this repository, we have tests to check we can bootstrap Cannot |
@andreabedini I have pushed a commit which will hopefully fix hadrian (https://gitlab.haskell.org/ghc/ghc/-/merge_requests/11274/diffs?commit_id=326719c1d5e43013b660e138536c8042c7e3f197). |
Any progress here? This sounds mildly alarming, but I have no clue. |
This was fixed on the ghc side and we successfully bumped the Cabal submodule. |
Oh, so I assume there's nothing to do cabal-side. Great, so this PR is closed-closed. |
In #8980 we started generating Lexer.hs with Cabal rather than as a external step. That PR forgets to remove the generatex file though which this PR rectifies.
Closes #9196
PS: now I wonder whether Cabal should complain/fail if an auto-generated file is already present in the source distribution. 🤔