public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: richarda@vecien.com To: gcc-gnats@gcc.gnu.org Subject: libstdc++/8836: char_traits<signed char> undefined at link time ( char_traits<char> is OK ) Date: Thu, 05 Dec 2002 16:26:00 -0000 [thread overview] Message-ID: <20021206001913.29155.qmail@sources.redhat.com> (raw) >Number: 8836 >Category: libstdc++ >Synopsis: char_traits<signed char> undefined at link time ( char_traits<char> is OK ) >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Dec 05 16:26:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: richarda@vecien.com >Release: 3.2.1 >Organization: >Environment: i386-pc-linux-gnu (RedHat 7.3) >Description: gint8 from glib is typedef signed char gint8; using basic_streambuf<gint8> fails at link with undefined reference to `std::char_traits<signed char>::eof()' undefined reference to `std::char_traits<signed char>::eq_int_type(unsigned long const&, unsigned long const&)' undefined reference to `std::char_traits<signed char>::eof()' undefined reference to `std::char_traits<signed char>::not_eof(unsigned long const&)' etc... Works fine if typedef is changed to use 'char' instead of 'signed char'. >How-To-Repeat: #include <istream> typedef signed char c_type; class buf : public std::basic_streambuf<c_type> { public: buf() { } virtual ~buf() { } }; int main (int argc, char * argv[] ) { buf * b = new buf; return 0; } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-12-06 0:26 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-05 16:26 richarda [this message] 2002-12-07 9:34 gdr
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=20021206001913.29155.qmail@sources.redhat.com \ --to=richarda@vecien.com \ --cc=gcc-gnats@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: linkBe 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).