[GHC] #10777: Overlong linker arguments on Windows leads to broken builds with confusing error messages
GHC
ghc-devs at haskell.org
Mon Aug 17 09:02:48 UTC 2015
#10777: Overlong linker arguments on Windows leads to broken builds with confusing
error messages
-------------------------------------+-------------------------------------
Reporter: snoyberg | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Compiler | Version: 7.10.2
Keywords: | Operating System: Windows
Architecture: | Type of failure: Compile-time
Unknown/Multiple | crash
Test Case: | Blocked By:
Blocking: | Related Tickets:
Differential Revisions: |
-------------------------------------+-------------------------------------
I've seen three different issues on Github about this: two in the stack
repo for stack users, and one in the yesod repo for a cabal sandbox user:
https://github.com/yesodweb/yesod/issues/1020
https://github.com/commercialhaskell/stack/issues/466
https://github.com/commercialhaskell/stack/issues/795
The problem comes down to this: Windows has a limit of 32k on the size of
a command string, which can be tripped by GHC's link phase when using a
large number of libraries. The ideal situation would be for GHC to have a
different way of passing large argument lists to the linker; I don't know
how feasible this is, but I wanted to open up a ticket before I started
investigating myself in case others have seen this.
--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/10777>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
More information about the ghc-tickets
mailing list