public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hklunder@legato.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/8580: undefined references to std::char_traits
Date: Wed, 20 Nov 2002 14:46:00 -0000	[thread overview]
Message-ID: <20021114123210.1575.qmail@sources.redhat.com> (raw)


>Number:         8580
>Category:       libstdc++
>Synopsis:       undefined references to std::char_traits
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 14 04:36:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     hklunder@legato.com
>Release:        3.2, and 3.3 20021113 (experimental) as well
>Organization:
>Environment:
RedHat Linux 7.3
intel Pentium
>Description:
Using a std::basic_string<short> causes undefined references to std::char_traits<short>::length(short const*) and to std::char_traits<short>::copy(short*, short const*, unsigned)
>How-To-Repeat:
compile undef.cpp using "g++ undef.cpp" and enjoy.
See readme.txt in the attached gzipped tar file for details.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-compressed; name="undef.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="undef.tgz"

H4sIALGj0z0AA+2W32vbMBDH8zpD/oeDwZq0jWPZScO80ZcR1tAxSrOnjZEpsmKL2pInyW3K2P++
s5P+SEdX6EhHhz4PiRXdnU4XfXXWnCYF9+3StrZGQIJgNBy2ghV3v4MhiVpocDAYheQgOkB7MhwN
WxBsL6UbKmOpBmhppf5YgofmnykTYKooRc4TqGTCFz4rS6AygVRZsBkHrrXSUHBjaMoNCLm2wxPj
e58yYSCjZcmlgQthMzjn2gglIfLDJszNOIIwCEJCSAQdviy5FgWXlubdOgwHhb9QK2QK5tJYXsAF
NXDKkyNq4YOQ1RJGGGKBuQhpeQ4n6Cyqwvcab9xEUS+XC8kbo9Wu6nAYJ/bSvb2b/XnNsI4/r0Ru
m8Rjz/f7RrNE6D5TciHSSnPo9bik85z3bKZRKMYr6BmHOR4FYzUtV0Mh8Qjlufev/8pHcV2ULa7x
kP7JcK3/YRREpNF/5PT/NLwUkuVVwuEtnmiUy2Hba3uoMCiokJ1aa0B1yvaBZVim3V0cnEMXfrS9
F8YmcTynRrDZyvetyZS2hzA3naD7Bi00t5WWEODzz/bz1Mf/zvVlvsU1HtA/CUejq/4fjAZBrf/B
YOD0/xT0bVH2GVt+v3j/+shXMUwkLCrJbN20v90j8X1oJuorYYZ9UFizlv56AruhYtQqfXUjHG5G
+SJkr3ZO+ddOY4HtGpvo7n3uzeyr7k7s3Um346ey8rHNnynJ8C3Wn33+OJ1PzNQSciu7iRlPKX6M
35HxybE5PZ6S2V6wJFE3Xr0V4FtDApovuOYYB6xab/33HcZxzmVqs428uzt3E9teHWfTGVPl5ax2
Mqss6rptVnEjt7+uGok2Fh2fGCzidFiXMAwfU8I61j2pV9KIFENhSZnKc85sGENeR65bCS5BgC+F
xfpQWxnXUxwOh8PhcDgcDofD4XA4HA6Hw+FwOByO2/wCwQ9t2gAoAAA=


             reply	other threads:[~2002-11-14 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 14:46 hklunder [this message]
2002-11-20 17:53 Gabriel Dos Reis
2002-11-20 17:55 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=20021114123210.1575.qmail@sources.redhat.com \
    --to=hklunder@legato.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: 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).