Date:	Sun, 29 Aug 1999 13:52:39 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Robert Hoehne <robert DOT hoehne AT gmx DOT net>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: RHIDE section in DJGPP.ENV
In-Reply-To:	<199908251657.SAA03977@robby.dittmannsdorf.de>
Message-ID:	<Pine.SUN.3.91.990829135212.9438L-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 25 Aug 1999, Robert Hoehne wrote:

> > + [rhide]
> > + RHIDE_TYPED_LIBS_DJGPP.cc=stdcxx
> > + RHIDE_TYPED_LIBS_DJGPP.cxx=stdcxx
> > + RHIDE_TYPED_LIBS_DJGPP.cpp=stdcxx
> > 
> 
> Only the following is needed:
> 
> [rhide]
> RHIDE_TYPED_LIBS_DJGPP.cc=stdcxx
> 
> since the other variables expand internally already to the
> ...cc variables if not overwritten by the user.

I thought I saw some reports of problems on c.o.m.d. that were solved
by defining the additional variables.  If they don't do any harm,
perhaps it's a good idea to add them anyway, e.g. for those die-hards
who still use the old RHIDE 1.4.

What about "RHIDE_TYPED_LIBS_DJGPP.f=g2c m", is it also expanded
internally?  I saw at least one problem report about g77, and Andris
suggested this as a solution.

> Theoretical there is no need for that section in djgpp.env, since
> I'll try to bring out a new RHIDE version before DJGPP 2.03, but
> just in case I'm not ready with it before the new DJGPP release
> this is a good idea.

Also, for those who won't upgrade, for love or money...

- Raw text -