From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-23877-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 30045 invoked by alias); 2 Nov 2002 13:16:05 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 30002 invoked by uid 71); 2 Nov 2002 13:16:04 -0000
Date: Sat, 02 Nov 2002 05:16:00 -0000
Message-ID: <20021102131604.29995.qmail@sources.redhat.com>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: Nicholas Wourms <nwourms@netscape.net>
Subject: Re: libstdc++/7849: libstdc++.so: undefined reference to std::messages<wchar_t>::do_get[...]
 causes failure during building of abi_check
Reply-To: Nicholas Wourms <nwourms@netscape.net>
X-SW-Source: 2002-11/txt/msg00091.txt.bz2
List-Id: <gcc-prs.sourceware.org>

The following reply was made to PR libstdc++/7849; it has been noted by GNATS.

From: Nicholas Wourms <nwourms@netscape.net>
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
        gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/7849: libstdc++.so: undefined reference to std::messages<wchar_t>::do_get[...]
 causes failure during building of abi_check
Date: Sat, 02 Nov 2002 08:05:39 -0500

 bkoz@gcc.gnu.org wrote:
 > Synopsis: libstdc++.so: undefined reference to std::messages<wchar_t>::do_get[...] causes failure during building of abi_check
 > 
 > Responsible-Changed-From-To: unassigned->bkoz
 > Responsible-Changed-By: bkoz
 > Responsible-Changed-When: Fri Nov  1 17:49:39 2002
 > Responsible-Changed-Why:
 >     Mine.
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: bkoz
 > State-Changed-When: Fri Nov  1 17:49:39 2002
 > State-Changed-Why:
 >     Can you confirm that this is still an issue?
 >     
 >     I'm unable to reproduce this with today's gcc, and ld as of:
 >     
 >     %ld --version
 >     GNU ld version 2.13.90 20021027
 >     
 >     -benjamin
 
 Sorry, yes this was fixed awile ago (probably before anyone 
 even got to this report).  Sorry for not closing it out.
 
 Cheers,
 Nicholas