From:	greve AT rs1 DOT thch DOT uni-bonn DOT de (Thomas Greve)
Subject:	Re: Beginner needs help!
To:	jz0t AT erctitan DOT me DOT wisc DOT edu (Jim Zurlo)
Date:	Tue, 9 Jun 92 15:48:49 NFT
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

> 
> Hi, 
> I would like to use djgpp to compile the output of f2c so that
> I can effectively get a free 32 bit Fortran compiler.  The first
Hm. Don't set your expectations that high. I got a real mode f2c
to run with djgcc, but the result was not exactly what i expected.

> problem is that I can't even get djgpp to run.  I'm using a 1Meg
> 386 machine. 
Go and get yourself 4 additional Megabytes.

> Do I need to have DEVICE=HIMEM.SYS in my CONFIG.SYS
> file? 
Depends on what else is in your memory. If you have a cache witch
uses extended memory, i'd say yes.

> Right now I'm using DOS 3.x, do I need to switch to DOS 5.0?
No. But the `x' should be a 3.

> When I try to compile some of the simple programs that came with
> the distribution there is disk activity while a swap file is opened
> and then everything stops.  Even leaving it run overnight doesn't
> get me any farther.
I started an erathostenes-sieve that occupied 80% of my physical ram
(8MB) one day. It was finished two minutes later. Then i started it 
with 120%. I aborted tho whole thing one and a half hour later. It had 
been accessing the HD permanently. The ability of paging is nice, but
don't rely on it too heavily.

> Has anyone else used djgpp and f2c?  Could you share any batch files
> you've written and any suggestions on what I can delete from djgpp
> since I certainly don't need the whole djgpp distribution just to
> compile Fortran programs.  
You need the compiler stages (cpp, cc1obj, as, ld) except for cc1plus.
You should use gcc, ar and some sort of make for convenience.
You need the libraries (libc, libgcc, libm) and the include files. 
You'll probably find all this in the djdev-package. 
You don't need any of the sources, the cplusinc-includes and that stuff
related to C++. Ah yes, and you can dump all that nice graphics stuff...

Some words about f2c. It procudes horribly inefficient C code, but the
code may probably be optimized by the gcc (use -O2).

The code produced by f2c doesn't always do what you expect it to do.
Things that should have appeared on stdout appeared in a file fortran.1
instead, file-io did not behave as it did on this workstation when 
compiled with a real fortan compiler.

So: f2c is no tool for quick turn around times, you always should expect
to be forced to look into the C code the one or other time.

> Thanks!
> Jim
> jz0t AT erctitan DOT me DOT wisc DOT edu
> 
> 


				- Thomas

   greve AT rs1 DOT thch DOT uni-bonn DOT de
   unt145 AT dbnrhrz1

- Raw text -