Date:	Sun, 3 May 1998 18:32:08 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Al Wong <awong AT primenet DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Various Questions for DJGPP
In-Reply-To:	<354B062D.670@primenet.com>
Message-ID:	<Pine.SUN.3.91.980503183131.19706h-100000@is>
MIME-Version:	1.0

On 2 May 1998, Al Wong wrote:

> 1) A large C program compiles and links successfully on a
>    Pentium 133Mhz with 40MB of RAM. The same program also
>    compiles but FAILS to link on a 486-33Mhz with 8 MB of RAM.
>    I get a SIGSEGV error. Possible solutions and fixes suggested
>    in the FAQ doesn't seem relevant to this problem. Does the current
>    version of DJGPP require "better" hardware than a 486?

No, 486 is not the problem, most likely.  It's the lack of memory that
probably causes the crash.  Run go32-v2 with no arguments and post
what it prints.  If the numbers it prints are small, the linker
doesn't have enough memory to run.  See section 7.2 of the FAQ.

> 2) How does one disable the "Time in ..." messages that the
>    compiler displays.

Did you use the -Q switch to GCC?  If so, don't.  If not, please post
the exact command line you use to compile and link the program; these
messages shouldn't be printed by default at all.

> 4) To get rid of all debugger information, is using the "-s" switch
>    in the compilation all that is needed?

You need to use -s during LINKING, not compilation.

- Raw text -