From: Benjamin Kosnik <bkoz@redhat.com>
To: Alexander Kabaev <ak03@gte.com>
Cc: rodrigc@attbi.com, gcc@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: _GLIBCPP_USE_WCHAR_T undefined in FreeBSD's c++config.h?
Date: Wed, 19 Feb 2003 20:07:00 -0000 [thread overview]
Message-ID: <20030219134544.7cff706a.bkoz@redhat.com> (raw)
In-Reply-To: <20030219132328.68570f7d.ak03@gte.com>
>FreeBSD does not implement iconv family functions in the base system, it
>has a WCHAR_MIN/WCHAR_MAX constants defined in a wrong header and wcstof
>function is not committed yet. These three prevent libstdc++ configure
>from enabling wchar_t instantiations.
Thanks, this was very informative. It's great news that this is so close
to working on FreeBSD.
-benjamin
next prev parent reply other threads:[~2003-02-19 19:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 18:07 Craig Rodrigues
2003-02-19 18:23 ` Benjamin Kosnik
2003-02-19 18:25 ` Alexander Kabaev
2003-02-19 20:07 ` Benjamin Kosnik [this message]
2003-02-20 18:11 ` Phil Edwards
2003-02-20 13:57 ` Craig Rodrigues
2003-02-19 19:11 ` Karel Gardas
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=20030219134544.7cff706a.bkoz@redhat.com \
--to=bkoz@redhat.com \
--cc=ak03@gte.com \
--cc=gcc@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=rodrigc@attbi.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: 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).