delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/07/12/11:48:38

From: pavenis AT lanet DOT lv
To: "Laurynas Biveinis" <lauras AT softhome DOT net>, djgpp-workers AT delorie DOT com
Date: Thu, 12 Jul 2001 18:48:35 +0300
MIME-Version: 1.0
Subject: Re: Comments on GCC 3.0 distribution
Message-ID: <3B4DF103.11332.D60645@localhost>
In-reply-to: <20010711214740.A333@lauras.lt>
References: <2427-Wed11Jul2001195622+0300-eliz AT is DOT elta DOT co DOT il>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

Sorry for empty response earlier today

On 11 Jul 2001, at 21:47, Laurynas Biveinis wrote:

> 
> > > Right. I've fixed this in CVS and made a fixincludes test for GCC to
> > > fix it during GCC build time. Does Andris distribute fixed file in bin
> > > distribution?
> > 
> > Obviously not: the above failure was with GCC 3.0 installed over
> > djdev203.
> 
> This should be fixed. Andris, can you put the fixed file in the GCC header
> directory? I see no linker script-alike problems here.

Maybe. Anyway I would want to hear some more feedback about 
binaries of gcc-3.0. I built them using current (at that time) CVS 
version of DJGPP.

Main question I would like to hear some feedback:

How behaves these binaries on Win2000. I don't have possibility to 
test it myself. If we have serious incompatibilities with Win2K, that 
cannot be fixed quickly enough, then perhaps it will be needed to 
rebuild using patched djdev203 (to avoid NTVDM crashes on nested 
DPMI tasks problem).

One more question is about linker script in gcc30b.zip:

Builtin script from bnu2112b.zip seems to be compatible with gcc-3.0
(all seems to work if I remove -Tdjgpp-x.djl from specs). Anyway
problem like:
	All my C++ programs crashes and GDB shows nonsense
	when I'm trying to debug this problem. All worked Ok with
	gcc-2.95.X
is too serious to be simply ignored. So I suggest to keep linker
script in GCC version specific directory identical with one from latest
version of binutils (currently 2.11.2). If user program or some package 
assumes that the name of this script will be djgpp.djl it is broken
and should be fixed (one should explicitly specify -T... to use custom
linker script)

Andris

PS. I'll be away beginning from Saturday possibly for up to 2 weeks.
      I may be able to read e-mail but there will be no gcc hacking  related
     activity at that time. So perhaps next update from me could happen
     not earlier than in begin of August (and release schedule of gcc
    says that we could expect gcc-3.0.1 at that time)


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019