Date: Wed, 9 Dec 1998 17:38:45 +0200
From: Alexander Bokovoy <bokovoy AT bspu DOT unibel DOT by>
X-Mailer: The Bat! (v1.15) S/N 137834AC
Organization: BSPU named after Maxim Tank
X-Priority: 3 (Normal)
Message-ID: <15735.981209@bspu.unibel.by>
To: Eli Zaretskii <djgpp AT delorie DOT com>
Subject: SPECS and DJGPP.DJL problem in DJGPP 2.02 and GCC 2.8.1 (was: DJGPP 2.02 and GCC 2.8.1 PROBLEM ...)
References: <Pine DOT SUN DOT 3 DOT 91 DOT 981209131829 DOT 8064I-100000 AT is>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Eli Zaretskii wrote:
> On Wed, 9 Dec 1998, Alexander Bokovoy wrote:
>> Definitely yes. Somebody should compare specs from GCC 2.8.1 and DJGPP 2.02
>> distribution and post combined version.
> I don't think it's a good idea to tell users to mess with lib/specs file,
> they might scrog their entire installation that way. I think both packages
> should include identical specs files.
You're right. But, as Andris stated, GCC's specs uses crtf.o which
isn't useful under DJGPP 2.02. Thus, both specs and djgpp.djl scripts
should be synchronized.
> (A better alternative would be to have this file in one package only, but
> that's impossible unless support for gcc 2.7.x is dropped.)
Probably  after  releasing  EGCS  1.1.1  for DJGPP, gcc 2.7.x could be
dropped? Then we'll have gcc 2.8.1.1 which is perfectly working with C
and  more  stable  than GCC 2.7.x, but has problems with C++, and EGCS
1.1.1, which is more useful for C++ developers. Also GCC 2.7.x has
many bugs and disfeatures in C++ implementation, the most known is
exception support.


Best regards,
Alexander Bokovoy, <bokovoy AT bspu DOT unibel DOT by>
= Linux ==============================================================
Though it is always possible to have a look at the world through the
Windows, people usually prefer not only to look but live in it too.
============================================================== Linux =