[webkit-dev] Building Win32/Release WebKit: linker error LNK1106
pei.wu at archermind.com
Tue Jan 26 23:10:43 PST 2010
Thank you for reply.
As I say in the title, I am doing a release build on winXP.
I try to set up SDK 7 as you suggested, and use /expectedoutputsize:120000000.
But it looks nothing help. The result is also LNK1106.
----- Original Message -----
From: "Marc-Antoine Ruel" <maruel at chromium.org>
To: "wupei" <pei.wu at archermind.com>
Cc: <webkit-dev at lists.webkit.org>
Sent: Wednesday, January 27, 2010 9:27 AM
Subject: Re: [webkit-dev] Building Win32/Release WebKit: linker error LNK1106
You didn't say on what flavor. I assume you are doing a release build.
If so, you probably need a x64 OS to link the static library.
You may want to install a few hotpatches from Microsoft,
lists a fews in addition to the ones listed at
http://webkit.org/building/tools.html. This is especially necessary
with the SDK 7 + VS2005 configuration.
Also, you may be interested in the workaround listed at
In short; use /expectedoutputsize:120000000
2010/1/25 wupei <pei.wu at archermind.com>:
> I am trying to build WebKit-r53371 on windows. But now i am blocked with
> this error when build the webcore project:
> Performing Pre-Link Event...
> Creating library...
> C:\cygwin\home\wupei\WebKit-r53371\webkitbuild\lib\WebCore.lib : fatal error
> LNK1106: invalid file or disk full: cannot seek to 0x5254F4AC
> Project : warning PRJ0018 : The following environment variables were not
> When I monitored the webcore.lib in the disk space, when "Creating
> library..." is in progress,
> WebKitBuild/lib/WebCore.lib is created and rapidly grows from a couple
> of megs to 128M, then to 256M, and at last to 512M, 1G. After LNK1106 error
> is displayed, the file is removed.
> Frist, The disk has more than 10GB free space when build the webkit, so I
> think it isn't because of the free space.
> Second, I have seen the Bug 19743 - Release build fails on 32-bit Windows
> (https://bugs.webkit.org/show_bug.cgi?id=19743), but my version is newer
> than the bug fixed one.
> Third, I have done update-webkit before build-webkit.
> And I also seen someone met the same problem in the network, but I can't
> search the solution.
> Dose anyone meet the same problem and have solved it? Will be appreciated
> for any comments.
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
More information about the webkit-dev