public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pere@hungry.com
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/3198: Missing wide char functions crashes compile
Date: Fri, 15 Jun 2001 09:26:00 -0000 [thread overview]
Message-ID: <20010615161823.21578.qmail@sourceware.cygnus.com> (raw)
>Number: 3198
>Category: libstdc++
>Synopsis: Missing wide char functions crashes compile
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri Jun 15 09:26:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: Petter Reinholdtsen
>Release: gcc 3.0 2001-06-15
>Organization:
>Environment:
Debian 2.2
>Description:
The current CVS refuses to compile on Debian 2.2, as a lot
of functions are missing. The attached patch hides the
problem by moving the missing functions into a #if 0 block
in libstdc++-v3/include/c_std/bits/std_cwchar.h.
The missing symbols are: fgetwc, fgetws, fputwc, fputws,
fwide, fwprintf, fwscanf, getwc, getwchar, putwc, putwchar
swprintf, swscanf, ungetwc, vfwprintf, vfwscanf, vswprintf
vswscanf, vwprintf, vwscanf, wcsftime, wprintf, wscanf
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="debian.diff"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="debian.diff"
SW5kZXg6IGxpYnN0ZGMrKy12My9pbmNsdWRlL2Nfc3RkL2JpdHMvc3RkX2N3Y2hhci5oCj09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT0KUkNTIGZpbGU6IC9jdnMvZ2NjL2djYy9saWJzdGRjKystdjMvaW5jbHVkZS9jX3N0ZC9i
aXRzL3N0ZF9jd2NoYXIuaCx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4xNgpkaWZmIC11IC1yMS4x
NiBzdGRfY3djaGFyLmgKLS0tIHN0ZF9jd2NoYXIuaAkyMDAxLzA2LzExIDA0OjM2OjU5CTEuMTYK
KysrIHN0ZF9jd2NoYXIuaAkyMDAxLzA2LzE1IDE2OjE1OjE1CkBAIC0xMjIsNyArMTIyLDggQEAK
IHsKICAgdXNpbmcgOjp3aW50X3Q7CiAKLSAgdXNpbmcgOjpidG93YzsKKyNpZiAwCisgIC8vIE5v
dCBwcmVzZW50IG9uIERlYmlhbiAyLjIKICAgdXNpbmcgOjpmZ2V0d2M7CiAgIHVzaW5nIDo6Zmdl
dHdzOwogICB1c2luZyA6OmZwdXR3YzsKQEAgLTEzMiwxMCArMTMzLDYgQEAKICAgdXNpbmcgOjpm
d3NjYW5mOwogICB1c2luZyA6OmdldHdjOwogICB1c2luZyA6OmdldHdjaGFyOwotICB1c2luZyA6
Om1icmxlbjsKLSAgdXNpbmcgOjptYnJ0b3djOwotICB1c2luZyA6Om1ic2luaXQ7Ci0gIHVzaW5n
IDo6bWJzcnRvd2NzOwogICB1c2luZyA6OnB1dHdjOwogICB1c2luZyA6OnB1dHdjaGFyOwogICB1
c2luZyA6OnN3cHJpbnRmOwpAQCAtMTQ3LDEzICsxNDQsMjIgQEAKICAgdXNpbmcgOjp2c3dzY2Fu
ZjsKICAgdXNpbmcgOjp2d3ByaW50ZjsKICAgdXNpbmcgOjp2d3NjYW5mOworICB1c2luZyA6Ondj
c2Z0aW1lOworICB1c2luZyA6OndwcmludGY7CisgIHVzaW5nIDo6d3NjYW5mOworI2VuZGlmCisK
KyAgdXNpbmcgOjpidG93YzsKKyAgdXNpbmcgOjptYnJsZW47CisgIHVzaW5nIDo6bWJydG93YzsK
KyAgdXNpbmcgOjptYnNpbml0OworICB1c2luZyA6Om1ic3J0b3djczsKICAgdXNpbmcgOjp3Y3J0
b21iOwogICB1c2luZyA6Ondjc2NhdDsKICAgdXNpbmcgOjp3Y3NjbXA7CiAgIHVzaW5nIDo6d2Nz
Y29sbDsKICAgdXNpbmcgOjp3Y3NjcHk7CiAgIHVzaW5nIDo6d2NzY3NwbjsKLSAgdXNpbmcgOjp3
Y3NmdGltZTsKICAgdXNpbmcgOjp3Y3NsZW47CiAgIHVzaW5nIDo6d2NzbmNhdDsKICAgdXNpbmcg
Ojp3Y3NuY21wOwpAQCAtMTcxLDggKzE3Nyw2IEBACiAgIHVzaW5nIDo6d21lbWNweTsKICAgdXNp
bmcgOjp3bWVtbW92ZTsKICAgdXNpbmcgOjp3bWVtc2V0OwotICB1c2luZyA6OndwcmludGY7Ci0g
IHVzaW5nIDo6d3NjYW5mOwogCiAgIHVzaW5nIDo6d2NzY2hyOwogCg==
next reply other threads:[~2001-06-15 9:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 9:26 pere [this message]
2001-06-26 17:24 bkoz
2001-12-15 8:24 rodrigc
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=20010615161823.21578.qmail@sourceware.cygnus.com \
--to=pere@hungry.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).