delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-bounces using -f |
X-Recipient: | djgpp AT delorie DOT com |
Date: | Sun, 30 Aug 2020 20:03:28 +0300 |
Message-Id: | <833644xdzz.fsf@gnu.org> |
From: | "Eli Zaretskii (eliz AT gnu DOT org) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com> |
To: | djgpp AT delorie DOT com |
In-Reply-To: | <e24eddbd-c85c-9142-32f2-fe9191d8ea69@gmx.de> (djgpp@delorie.com) |
Subject: | Re: SIGSEGV when trying to compile helloworld |
References: | <f39d7f31-8815-e9fe-7ac1-4b8551098a59 AT gmx DOT de> |
<835z90xgab DOT fsf AT gnu DOT org> <e24eddbd-c85c-9142-32f2-fe9191d8ea69 AT gmx DOT de> | |
Reply-To: | djgpp AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
> From: "sleepy_dog AT gmx DOT de [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com> > Date: Sun, 30 Aug 2020 18:32:41 +0200 > > go32/v2 version 2.0 built Oct 18 2015 09:41:08 > Usage: go32 coff-image [args] > Rename this to go32.exe only if you need a go32 that can run v2 binaries as > well as v1 binaries (old makefiles). Put ahead of the old go32 in > your PATH > but do not delete your old go32 - leave it in the PATH after this one. > Set GO32_V2_DEBUG=y in the environment to get verbose output. > > DPMI memory available: 704964 Kb > DPMI swap space available: 0 Kb > > Hm. DPMI swap space 0 = bad? No, that's OK. Many "modern" DPMI providers just lump all the memory together (700MB in your case), and don't bother separating them into RAM and swap. The memory amount sounds enough, so I'm puzzled what could be the problem. Maybe some Windows 7 specific problem? I think someone posted here long ago tricks to get the Windows DPMI provider more friendly... Anyone?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |