Home Dashboard Directory Help
Search

Visual Studio 2005 SP1 reproducible linker error (LKN1257 caused by C1083) by bhearsum


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 581207
Opened: 7/29/2010 2:49:32 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

We've been hitting a 100% reproducible linker crash which we believe to be hitting the 32-bit address space limit. The machine in question has the /3gb flag enabled in boot.ini. The error it spits out looks like this:
fatal error C1083: Cannot open compiler intermediate file: '../../staticlib/components/gklayout.lib': Not enough space
LINK : fatal error LNK1257: code generation failed

I've seen similar bugs posted on Connect, such as http://connect.microsoft.com/VisualStudio/feedback/details/521439/link-failure-lnk1106-on-ltcg-for-a-static-library. I'm hoping that there's an answer to this that involves a hotfix, rather than a big upgrade.
Details
Sign in to post a comment.
Posted by rajalist on 3/14/2014 at 10:57 PM
I also need the hotfix. how can i get it.
Posted by pscj007 on 3/22/2011 at 5:27 AM
I need the hotfix,could you tell me how can I get it.thanks .my email: pscj@qq.com
Posted by bhearsum on 8/9/2010 at 8:10 AM
Thanks for getting back to me on this. I'm not sure we'll be able to move to VS2010 right away, but we've worked around the issue by linking directly to object files rather than libs.
Posted by Microsoft on 8/7/2010 at 4:14 PM
This out-of-memory issue has been fixed in VS 2010. I tried the provided link repro on a 32-bit Win7 (x86) machine, and the linking finished successfully, with virtual memory usage peaked at about 1.6GB. Please try VS 2010. If you need a hotfix of this issue for an old-versioned VS, please contact Microsoft PSS.

Thanks for your bug report.
Posted by Microsoft on 7/30/2010 at 5:06 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.