Closed mbj closed 1 year ago
Oh wow that looks annoying. I'm assuming it is because there are so many modules?
@jdjacobrli I assume it happens at the moment the various smaller modules get assembled into a bigger package, and each module is likely referenced with an absolute path, overflowing the character limit.
I'm sure there is a workaround, but blocked by private issues for the next 60min. Will post my progress on debugging this.
This is a public build showing the issue, this is with stack --verbose
. Not showing the full CLI.
I suspect its the github actions environment leading to longer paths. https://github.com/mbj/stack-deploy/runs/1445686795?check_suite_focus=true#step:6:11422
For anyone watching here the issue is the number of modules running into OSX specific limits on the command line size.
The trick will be to split up this project into many, one per AWS service. Not only removing this issue class altogether, but also making compilation much faster as users will (just like with amazonka) only have to build the subprojects for the AWS features they actually use.
This was addressed via #207 (unreleased yet).
I know this is essentially more an issue with stack/cabal/ghc.
Still as this projects triggers it I'm asking here if anyone knows a workaround to get a rid of:
This is using
stack-2.5.1
on Github actions.As I'm posting this I'm rebuilding with verbosity to find the exact GHC command.
I hope its okay I ask for input here, as I assume others may have hit it already and have a workaround. If such a workaround is found: I'm happy to PR it to this projects README. As it'll allow others that will hit this issue to work with this great project efficiently.