Date:	Mon, 15 May 2000 10:51:43 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp AT delorie DOT com
Subject:	Re: OT: RHIDE and G77 (FORTRAN 77)
In-Reply-To:	<391f05bc_2@news1.his.com>
Message-ID:	<Pine.SUN.3.91.1000515105109.9209L-100000@is>
MIME-Version:	1.0
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

On Sun, 14 May 2000, Lawrence Robins wrote:

> Now I find that renaming or copying RHIDE_.ENV to RHIDE.ENV
> (as Mr. Frounze suggests), with no other changes, fixes the
> problem.
> 
> Furthermore, editing DJGPP.ENV to change
>    RHIDE_TYPED_LIBS_DJGPP.f=g2c m
> to
>    RHIDE_TYPED_LIBS.f=g2c m
> with no other changes (i.e., don't create RHIDE.ENV from
> RHIDE_.ENV in this case) also fixes the problem.

The same problem was fixed in previous versions of GCC and RHIDE by
defining RHIDE_TYPED_LIBS_DJGPP.f.  That's why this variable was added
to DJGPP.ENV.  If the reason for these new problems is that RHIDE was
changed, I think this is an unfortunate change.  I wish people would
refrain from making such changes, to avoid breaking something that
took a long time to make work.

> To summarize, the correct fix is to put the line
>    RHIDE_TYPED_LIBS.f=g2c m
> in either RHIDE.ENV, or the [rhide] section of DJGPP.ENV.

I would argue that, rather than change DJGPP.ENV, RHIDE should be
changed to use RHIDE_TYPED_LIBS_DJGPP.f, as it did previously.

- Raw text -