-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
building amazonka-ec2 with stack using ~7GB #549
Comments
Stack builds packages in parallel by default I believe - try turning that off so only one package is built at a time? |
|
and another time:
|
[280 of 280] Compiling Network.AWS.EC2 gcc: error: .stack-work/dist/x86_64-linux/Cabal-3.0.0.0/build/Network/AWS/EC2/Types/Product.dyn_o: No such file or directory `gcc' failed in phase `Linker'. (Exit code: 1) also -- While building package amazonka-ec2-1.6.1 using: /var/stackage/.stack/setup-exe-cache/x86_64-linux/Cabal-simple_mPHDZzAJ_3.0.0.0_ghc-8.8.1 --builddir=.stack-work/dist/x86_64-linux/Cabal-3.0.0.0 build lib:amazonka-ec2 test:amazonka-ec2-test --ghc-options "" Process exited with code: ExitFailure (-9) (THIS MAY INDICATE OUT OF MEMORY) Logs have been written to: /var/stackage/work/unpack-dir/.stack-work/logs/amazonka-ec2-1.6.1.log Preprocessing library for amazonka-ec2-1.6.1.. Building library for amazonka-ec2-1.6.1.. [ 3 of 280] Compiling Network.AWS.EC2.Types.Product
This is fairly well trodden territory by now - there's little short term I can do to affect how much memory varying versions of GHC use when compiling the libraries. There is discussion around splitting the graph of generated types into modules based on their SCCs or some other boundary to alleviate the fact |
There was a GHC ticket raised about this recently. While we will try to improve things in the long term. However, given that the current situation seems barely tenable there are a few things that you might consider doing in the short term as well:
I will say that even with |
The large |
Right. I have been building |
@bgamari Is this still bad, now that the pattern synonym stuff is in |
The pattern synonyms change itself has little to no impact on compilation performance - it's the quadratic core which is detailed in Edkso's Avoiding quadratic core code size with large records that we've always been subject to. We are already generating one-type-per-module on |
We are trying to build amazonka-ec2-1.6.1 with ghc-8.8.1 on Linux for Stackage Nightly using stack-2.1.3 and ghc is using a lot of memory: about 6.8GB, which may be causing problems.
Not sure if anything can be done, but thought I would report it here.
The text was updated successfully, but these errors were encountered: