public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Nicholas Wourms <nwourms@netscape.net>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
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 05:16:00 -0000 [thread overview]
Message-ID: <20021102131604.29995.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2002-11-02 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 5:16 Nicholas Wourms [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-02 7:02 bkoz
2002-11-01 17:49 bkoz
2002-09-07 7:46 Andrew Pinski
2002-09-07 4:56 nwourms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021102131604.29995.qmail@sources.redhat.com \
--to=nwourms@netscape.net \
--cc=bkoz@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).