Add support for "reponse files" to workaround Windows command line length limitations
|Reported by:||joeyhess||Owned by:||snoyberg|
|Type of failure:||None/Unknown||Test Case:|
|Related Tickets:||#10777 #9685||Differential Rev(s):|
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?
Change History (16)
comment:4 Changed 2 years ago by
|Architecture:||x86 → Unknown/Multiple|
|Summary:||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)" → Add support for "reponse files" to workaround Windows command line length limitations|
|Type:||bug → feature request|