public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Joshua Kwan <joshk@triplehelix.org>
To: cygwin@cygwin.com
Subject: wide string methods, round two
Date: Sun, 28 Sep 2003 08:07:00 -0000	[thread overview]
Message-ID: <20030928041610.GA13447@firesong> (raw)

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Sorry I was not able to respond to helpful replies on this list due to
the lack of "CC me on reply"-age. Luckily, I had the presence of the
mind to check cygwin.com/ml/cygwin :)

Anyway, some sed work got me this conclusive list of missing functions:

assign(wchar_t*, unsigned, wchar_t)
compare(wchar_t const*, wchar_t const*, unsigned)
copy(wchar_t*, wchar_t const*, unsigned)
length(wchar_t const*)
move(wchar_t*, wchar_t const*, unsigned)

for namespace std, templated class char_traits, in the case that this is
more clear to some people who have glazed over while trying to read the
error messages.

I nm'd libstdc++.a for these and got a number of likely results, but
these were probably for different classes.

The source of the problem maybe lies in the g++ source? That's where
libstdc++ is built anyhow. Are there build logs available anywhere for
binary packages built for Cygwin? I'm not as comfy with STL as I'd like
to be so I don't have much of an idea where to look.

Again, please CC me on replies.

Thanks,

-- 
Joshua Kwan

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

             reply	other threads:[~2003-09-28  4:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28  8:07 Joshua Kwan [this message]
     [not found] <AEECC0E5FA0760449436D74422C4D46F028B9E22@xboi25.boise.itc.hp.com>
2003-10-07  0:41 ` Joshua Kwan

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=20030928041610.GA13447@firesong \
    --to=joshk@triplehelix.org \
    --cc=cygwin@cygwin.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).