Sender:	nate AT cartsys DOT com
Message-ID:	<3754B255.5AE7B5E0@cartsys.com>
Date:	Tue, 01 Jun 1999 21:25:57 -0700
From:	Nate Eldredge <nate AT cartsys DOT com>
X-Mailer:	Mozilla 4.08 [en] (X11; I; Linux 2.2.5 i586)
MIME-Version:	1.0
To:	djgpp AT delorie DOT com
Subject:	Re: libf2c.a library and "f2c" vs "g77"
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990601092741 DOT 19912G-100000 AT is> <3 DOT 0 DOT 5 DOT 32 DOT 19990601105617 DOT 007c6210 AT jafar DOT uqar DOT uquebec DOT ca>
Reply-To:	djgpp AT delorie DOT com

Karel Uhlir wrote:
> 
> Thanks Andris and "DoLL",
> 
> I did finally succeed to compile under DOS (with "g77"), with the straight
> forward "good old" command line. That works fine.
> 
> I figured, as you suggested that the bug was under "Rhide", which I was
> about to abandon. But the solution that you have given now seems to work
> fine (see below).
> 
> Anyone else who has this problem under Rhide just has to add a line in the
> Rhide.env file as explained.
> 
> Thank you all for your technical advice.
> 
> Last question: If I understand well, g77 has grown from f2c? Does g77
> "include" f2c? What exactly is the difference? Which is better?

AFAIK, f2c converted Fortran to C code.  One could then use a C compiler
and a supplied library to actually compile and link it.  g77 is a front
end to GCC, so it compiles Fortran natively.  I believe it still uses
the f2c library (or some hacked version), however.
-- 

Nate Eldredge
nate AT cartsys DOT com

- Raw text -