Bug 45293 - Not enough space message when building webkit‏
Summary: Not enough space message when building webkit‏
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC Windows 7
: P2 Major
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-07 06:19 PDT by ljgeneral
Modified: 2017-03-20 19:36 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ljgeneral 2010-09-07 06:19:21 PDT
when building webkit revision 66795 using webkit/webkit/webkittools/scripts/build-webkit. I get following ouput

Output Window
 	 	

Performing Pre-Build Event...
/usr/bin/bash
cl : Command line warning D9040 : ignoring option '/analyze'; Code Analysis warnings are not available in this edition of the compiler
tmp.cpp
找不到文件 - *
复制了 0 个文件
Performing Pre-Link Event...
已复制         1 个文件。
已复制         1 个文件。
Linking...
fatal error C1083: Cannot open compiler intermediate file: 'C:\cygwin\home\hxl\webkit\WebKitBuild\lib\WebKitLib.lib': Not enough space
LINK : fatal error LNK1257: code generation failed
Project : warning PRJ0018 : The following environment variables were not found:
$(PRODUCTION)
$(DXSDK_DIR)
Build machine environment variables may not be correct.

My operation system  is Win7,I have got 32bit Microsoft Visual C++ 2005 Express Edition .I have 15G free space on this drive and 4G of ram.
 
I do not know how to past this error.
when I  search this question on google, Some suggestion is to disable some parts of Webkit you don't need. But I do not know how to disable it.
   thanks.
Comment 1 Adam Roben (:aroben) 2010-09-07 11:18:42 PDT
This happens from time to time as the size of WebCore.lib grows. link.exe runs out of virtual address space, leading to the error message you see. It has nothing to do with the amount of RAM or free hard drive space you have.

In the past, we've fixed this by combining multiple .cpp files into one (see, e.g., SVGAllInOne.cpp). You can also work around it by doing one of the following:

1) Building on a 64-bit version of Windows
2) Turning off LTCG
3) Doing a debug build