From: johnp3 AT idt DOT net (Xyloplax)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: g77 compiling problem
Date: Mon, 02 Jun 1997 20:38:53 GMT
Organization: Damage, Inc
Lines: 27
Message-ID: <33932d76.683911@news.idt.net>
References: <338f68dc DOT 1399793 AT news DOT idt DOT net> <5mr5rh$j6o AT freenet-news DOT carleton DOT ca>
NNTP-Posting-Host: ppp-28.ts-9.nyc.idt.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

On 1 Jun 1997 06:46:09 GMT, ao950 AT FreeNet DOT Carleton DOT CA (Paul
Derbyshire) wrote:


>
>My God! What are you compiling that needs 36 *megabytes*? Anyways, that's
>after a 7 meg allocation, for 45 megs total...more than your 40. Be sure
>to run g77 from pure DOS, not Windows at all, so CWSDPMI runs and provides
>disk swap. Have at least 10 megs of free disk space.
>
hehe these are molecular modelling programs that are usually run on a
Cray or at least an RS6k when researchers are going for accuracy and
the data are intended for publication, to give you an indication of
the calculating power. I plan to use the lowest and most approximate
options in order to run it on my PC since I neither need accuracy nor
do I intend to publish.
Well you were right about dos mode, but as I said , I tried dos mode
before. The problem was that I made a custom batch file just for the
unprocessed input files and I made the most pathetic mistake: -O3 was
-o3 in my bat file, so I had sucessively overwritten unoptimized
object files named "3" being produced! Once I made the correction and
ran it in dos mode again, it worked. Thanks and sorry for wasting your
time!:P
--
John Pavlakis
johnp3 AT idt DOT net
"You can lead a yak to water, but you can't teach an old dog to make a silk purse out of a pig in a poke." -- Opus Penguin