[Qt-interest] [Mingw-w64-public] "Memory exhausted" ld error when building Qt 4.8.0-rc1 with mingw-w64 4.7.0

[K. Frank]

Hello Ruben and Everyone!

The short answer is that I have managed to complete the build by re-running
make after freeing up some memory.

On Wed, Oct 19, 2011 at 2:20 PM, Ruben Van Boxem
<vanboxem.ruben at gmail.com> wrote:
> 2011/10/19 K. Frank <kfrank29.c at gmail.com>
> ...
>>
>> (It appears that my "Memory exhausted" error is occurs during the
>> debug part of the build process.)
>> ...
>
> On the page file size: that seems ok. I didn't modify the Windows defaults.
> I'm still kind of dazzled by this, I never encountered it.

Based on Ruben's success in building Qt on a similarly sized system,
I decided that maybe I was on the edge of having enough memory for
the build.

Again, after the failed build had exited, task manager reported about
2 GB of available memory (out of 4 GB).

So I rebooted my machine, went through task manager and killed off
various processes that looked unnecessary.  After doing this, task
manager reported about 3 GB of available memory.  When I re-ran
make, it picked up where it had left off -- linking QtGui4d.dll.  That took
about 45 minutes, but succeeded.  (QtGui4d.dll is about 456 MB in
size.)

(One note:  I wasn't watching memory usage while QtGui4d.dll was
being linked, but when the non-debug version, QtGui4.dll, was being
linked, memory usage (for all processes in the system, not just ld)
started at about 1 GB and grew more or less linearly to about 2.5 to
3 GB.  QtGui4.dll is about 13 MB in size.)

So...  I guess the moral of the story is that 2 GB of available memory
isn't quite enough for the build process, but 3 GB is.  (Just to be clear,
I didn't change the configuration or set any build flags to reduce memory
usage -- I just re-ran the build after re-booting and freeing up some memory
on my system.)

I did check that the 4.8.0-rc1 Qt build is basically working by building a
very simple test application, but I haven't used it for anything significant
yet.

> ...
> Ruben

Thanks for everyone's advice.


K. Frank