MinGW-w64 - for 32 and 64 bit Windows / Bugs / #348 Make: virtual memory exhausted

#348 Make: virtual memory exhausted

Milestone: v1.0 (example)

Status: closed-fixed

Owner: niXman

Labels: None

Priority: 5

Updated: 2014-07-14

Created: 2013-10-13

Creator: Dmitry KX

Private: No

The system is Windows 7 32-bit. GCC 4.8.1 from https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-posix/sjlj/

Calling my target:

mingw32-make -f Makefile.THT-app.Release distbin

...

echo Source: "F:/trading/soft/THT\LICENSE-LGPL-2.1.txt"; DestDir: "{app}"; Flags: ignoreversion >> tht-2.0.0.iss
echo Source: "F:/trading/soft/THT\LICENSE-LGPL-3.txt"; DestDir: "{app}"; Flags: ignoreversion >> tht-2.0.0.iss
mingw32-make.EXE: *** virtual memory exhausted.  Stop.
mingw32-make.EXE: *** Waiting for unfinished jobs....

The previous version from https://sourceforge.net/projects/mingwbuilds/files/host-windows/releases/4.8.1/32-bit/threads-posix/sjlj/ works fine

1 Attachments

Makefile.THT-app.zip

Discussion

Dmitry KX - 2013-10-18

4.8.2 has the same bug

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

niXman - 2013-10-18

I'm here)
Please wait, this weekend I going to analyze this problem.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

niXman - 2013-10-19

GCC 4.8.1 from https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/4.8.1/threads-posix/sjlj/

What revision is used?

The previous version from https://sourceforge.net/projects/mingwbuilds/files/host-windows/releases/4.8.1/32-bit/threads-posix/sjlj/ works fine

The same question.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Dmitry KX - 2013-10-19
  
  The latest versions:
  
  1) i686-4.8.1-release-posix-sjlj-rt_v3-rev2.7z and i686-4.8.2-release-posix-sjlj-rt_v3-rev0.7z from mingw-w64 repo. Buggy versions.
  
  2) x32-4.8.1-release-posix-sjlj-rev5.7z from mingwbuilds repo. Working version.
  
  Last edit: Dmitry KX 2013-10-19
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dmitry KX - 2013-10-26

Any progress with that? Speaking frankly I delayed the release of my own development toolchain based on mingwbuilds and Qt4 for three weeks because of this bug. I'd like to distribute the latest version 4.8.2. I believe that reverting make to 3.99.91 (like in x32-4.8.1-release-posix-sjlj-rev5.7z) will fix the bug. What is your opinion? Do we have any reason not to do that? Thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

niXman - 2013-10-26

I am in process.

my own development toolchain based on mingwbuilds and Qt4

What's the point? Why not use these builds of Qt{4,5}+mingw-w64+QtCreator?
https://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds/

Last edit: niXman 2013-10-26

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Dmitry KX - 2013-10-26
  
  I use some patches for Qt plus SJLJ mingw (this toolchain is not for public use).
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

niXman - 2013-10-26

As a workaround: just copy mingw32-make.exe from x32-4.8.1-release-posix-sjlj-rev5.7z into distribution package.

Last edit: niXman 2013-10-26

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dmitry KX - 2013-10-29

Ok, this is fixed in the latest update, thanks!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

niXman - 2013-10-30

status: open --> closed-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.