public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, pere@hungry.com Subject: Re: libstdc++/3198: Missing wide char functions crashes compile Date: Tue, 26 Jun 2001 17:24:00 -0000 [thread overview] Message-ID: <20010627002429.24779.qmail@sourceware.cygnus.com> (raw) Synopsis: Missing wide char functions crashes compile Responsible-Changed-From-To: unassigned->bkoz Responsible-Changed-By: bkoz Responsible-Changed-When: Tue Jun 26 17:24:29 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: open->feedback State-Changed-By: bkoz State-Changed-When: Tue Jun 26 17:24:29 2001 State-Changed-Why: I dunno folks. These are being checked, as part of acinclude.m3's GLIBCPP_CHECK_WCHAR_T_SUPPORT: dnl Checks for names injected into std:: by the c_std headers. AC_CHECK_FUNCS(btowc wctob fgetwc fgetwc fgetws fputwc fputws fwide \ fwprintf fwscanf swprintf swscanf vfwprintf vfwscanf vswprintf vswscanf \ vwprintf vwscanf wprintf wscanf getwc getwchar mbsinit mbrlen mbrtowc \ mbsrtowcs wcsrtombs putwc putwchar ungetwc wcrtomb wcstod wcstof wcstol \ wcstoul wcscpy wcsncpy wcscat wcsncat wcscmp wcscoll wcsncmp wcsxfrm \ wcscspn wcsspn wcstok wcsftime wcschr wcspbrk wcsrchr wcsstr,, \ ac_wfuncs=no) ?? I suspect that this was fixed in the actual release. Could your libc headers used at configure time be different than say /usr/include/wchar.h? -benjamin http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3198&database=gcc
next reply other threads:[~2001-06-26 17:24 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-26 17:24 bkoz [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-15 8:24 rodrigc 2001-06-15 9:26 pere
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=20010627002429.24779.qmail@sourceware.cygnus.com \ --to=bkoz@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=pere@hungry.com \ /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).