-
Notifications
You must be signed in to change notification settings - Fork 0
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
Build GHC with cabal-install and a Makefile #3
base: tmp/make-build-offset
Are you sure you want to change the base?
Conversation
Current status: it builds some ghc program in |
Ah, I need to pass some environment variable to |
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.
Thank you @hsyl20 this looks like a great start!
Now it seems like cabal doesn't like empty package databases:
Edit: that was my mistake (a debug statement in ghc-pkg...). Now it works. |
Effectively we want to completely disable the solver. We can add |
I've disabled it for stage1 where we start fresh to build boot libraries. |
4f9641d
to
563f2cf
Compare
09d2c38
to
1df74eb
Compare
f9fe095
to
7dde6ba
Compare
I get the same failure as on CI:
Is |
We should perhaps use |
I did set it in CI. CC=gcc, CXX=g++
worth a try. |
Unexpected failures in the testsuite should be all addressed. Now I need to address unexpected passes |
We basically revert https://gitlab.haskell.org/ghc/ghc/-/merge_requests/9418 It doesn't fail for our statically-built GHC, so it could be Alpine/musl specific.
Two unexpected passes left: The weird thing is that they don't pass locally... I'll try to debug this. |
Especially wrong for FrontendPlugins
"Fixed" by nuking |
Last test is now fixed. |
Note that we need a patched cabal: https://github.com/hsyl20/cabal/tree/hsyl20/per-file-extra-source-options