X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: pavenis AT lanet DOT lv
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Date: Fri, 17 May 2002 12:58:06 +0300
MIME-Version: 1.0
Subject: Re: gcc 3.1
Cc: djgpp-workers AT delorie DOT com
Message-ID: <3CE4FE5E.25829.48C43F@localhost>
In-reply-to: <9791-Fri17May2002124751+0300-eliz@is.elta.co.il>
References: <Pine DOT A41 DOT 4 DOT 05 DOT 10205171044150 DOT 16248-100000 AT ieva06> (message from	Andris Pavenis on Fri, 17 May 2002 10:51:41 +0300 (WET))
X-mailer: Pegasus Mail for Windows (v4.01)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body
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
Precedence: bulk

On 17 May 2002 at 12:47, Eli Zaretskii wrote:

> > Date: Fri, 17 May 2002 10:51:41 +0300 (WET)
> > From: Andris Pavenis <pavenis AT lanet DOT lv>
> > 
> > gcc-3.1 should works with binutils-2.11.2 or 2.12, but with these versions
> > one will get weird additional error messages on unresolved references
> > 
> > http://gcc.gnu.org/ml/gcc/2002-05/msg01385.html
> 
> Does this happen only with DWARF2 debug info (i.e. under -ggdb), or
> even with -g and -gstabs+, or without debug info at all?  If the
> latter, I think it's very bad.

with -gdwarf-2 only
> 
> > binutils-2.12.1 is recommended
> 
> If GCC 3.1 can only work without these warnings when used with
> Binutils 2.12.1 and later, I think we should try to convince GCC
> developers to fix that somehow before GCC 3.1 is released: Binutils
> 2.12.1 is not even on ftp.gnu.org yet, and 2.12 was only released 2
> months ago.  How can they reasonably require such a fresh version??
> 
> Or is it too late to ask them to change their minds?
 
Unlikely. Anyway it's not a fatal problem, as it happens only then when
one uses DWARF-2 debugging info and already have unresolved 
references from linker (so nothing is additionally broken, not counting
already broken user program ... )

Only we should be prepared for storm of questions about these messages.

Andris