From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date: Wed, 28 Mar 2001 12:56:26 +0300
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Test binaries of gcc-3.0 20010314 (prerelease)
Message-ID: <3AC1DF7A.9994.572567@localhost>
References: <20010327215541 DOT B2267 AT lauras DOT lt>
In-reply-to: <Pine.SUN.3.91.1010328113331.4337I-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

On 28 Mar 2001, at 11:33, Eli Zaretskii wrote:

> 
> On Tue, 27 Mar 2001, Laurynas Biveinis wrote:
> 
> > > installation (eg. gcc.exe etc is put in $DJDIR/bin2 instead of 
> > > $DJDIR/bin, so put it in Your path and You can use it) and that
> > 
> > What about introducing $DJDIR/local hierarchy? 
> 
> As far as I understand, the only thing that is needed to have several
> versions of GCC coexist on the same machine is to rename one of the
> gcc.exe drivers to a different name, such as gcc-2952.exe.  Each
> version of GCC should be able to find its own headers, specs, compiler
> passes, and libgcc.a automatically, and the single entry in the [gcc]
> section of DJGPP.ENV is IIRC redundant (if not, you need to add
> another section [gcc-2952]).

I have begun using different bin directory for such files (in my case
$DJDIR/bin2) already for sime time. I configured gcc-3.0 snapshot
using --enable-version-specific-runtime-libs so location of
libstdc++ headers doesn't overlap. Only possible problem I see is
possibility to try to link with wrong libstdcxx.a if $DJDIR/lib is explicitly
specified in libraries search directories. For gcc-3.0 dev. version
I put it in $DJDIR/lib/gcc-lib/djgpp/3.0/

Also one can unpack archive for example in directory d:/foo/bar
and add d:/foo/bar/bin2 at begin of the path and all should work.
It's should not be required to install gcc-3.0 development versions
for DJGPP under $DJDIR (it's different from earlier GCC version)

Andris

PS. I forgot to mention earlier. LFN is REQUIRED for these binaries.
(It's not an official version of course, so I think it's Ok now)