public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	pieter.winter@group2000.nl
Subject: Re: libstdc++/5090: linking fails when using std::basic_stringstream<wchar_t>
Date: Wed, 06 Nov 2002 09:50:00 -0000	[thread overview]
Message-ID: <20021106175010.22288.qmail@sources.redhat.com> (raw)

Synopsis: linking fails when using std::basic_stringstream<wchar_t>

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Nov  6 09:50:06 2002
State-Changed-Why:
    I could almost link the small program you had, only one
    symbol missing, with 3.0.4, but the problem got worse
    with 3.2:
    
    atlas2/wolf> /data/user/software/sparc-sun-solaris2.7/gcc-3.0.4/bin/c++ x.cc
    Undefined                       first referenced
     symbol                             in file
    std::_Format_cache<wchar_t>::_Format_cache()/var/tmp/ccHe092m.o
    ld: fatal: Symbol referencing errors. No output written to a.out
    collect2: ld returned 1 exit status
    
    
    atlas2/wolf> /data/user/software/sparc-sun-solaris2.7/gcc-3.2.0/bin/c++ x.cc
    Undefined                       first referenced
     symbol                             in file
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::good() const/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::exceptions() const/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::tie() const/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::setstate(std::_Ios_Iostate)/var/tmp//cc3CMB6T.o
    std::basic_streambuf<wchar_t, std::char_traits<wchar_t> >::sputn(wchar_t const*, int)/var/tmp//cc3CMB6T.o
    std::char_traits<wchar_t>::eq(wchar_t const&, wchar_t const&)/var/tmp//cc3CMB6T.o
    std::basic_stringstream<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::~basic_stringstream [in-charge]()/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::widen(char) const/var/tmp//cc3CMB6T.o
    std::basic_streambuf<wchar_t, std::char_traits<wchar_t> >::pubsync()/var/tmp//cc3CMB6T.o
    std::basic_stringstream<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::basic_stringstream[in-charge](std::_Ios_Openmode)/var/tmp//cc3CMB6T.o
    std::char_traits<wchar_t>::assign(wchar_t*, unsigned, wchar_t)/var/tmp//cc3CMB6T.o
    std::char_traits<wchar_t>::copy(wchar_t*, wchar_t const*, unsigned)/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::fill() const/var/tmp//cc3CMB6T.o
    std::basic_ios<wchar_t, std::char_traits<wchar_t> >::rdbuf() const/var/tmp//cc3CMB6T.o
    ld: fatal: Symbol referencing errors. No output written to a.out
    collect2: ld returned 1 exit status

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5090


             reply	other threads:[~2002-11-06 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  9:50 bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-12  0:06 Pieter Winter

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=20021106175010.22288.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pieter.winter@group2000.nl \
    /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).