[GHC] #8596: windows link failure due to excessively long gcc commad line "Unable to start C:\Program Files\Haskell + Platform\2013.2.0.0\mingw\bin/realgcc.exe (error code: 87)"

[GHC]

#8596: windows link failure due to excessively long gcc commad line "Unable to
start C:\Program Files\Haskell +
Platform\2013.2.0.0\mingw\bin/realgcc.exe (error code: 87)"
----------------------------+---------------------------------
       Reporter:  joeyhess  |             Owner:
           Type:  bug       |            Status:  new
       Priority:  normal    |         Milestone:
      Component:  Compiler  |           Version:  7.6.3
       Keywords:            |  Operating System:  Windows
   Architecture:  x86       |   Type of failure:  None/Unknown
     Difficulty:  Unknown   |         Test Case:
     Blocked By:            |          Blocking:
Related Tickets:            |
----------------------------+---------------------------------
 I have a program (git-annex) which builds successfully on windows, but
 when I enable any of three optional features which pull in some additional
 libraries, it fails to link.

 I will attach the output of cabal build --ghc-options=-v for a failing and
 a successful build.

 I hypothesize this is due to a command line length limit. The final
 failing gcc link command is 43814 characters, vs 30765 in the
 configuration that succeeds. Right around the 32k boundry.

 Not sure what I can do to work around this, short of splitting up my
 program into standalone libraries which will link without referencing
 every individual module?

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/8596>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler