From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Herbert" To: "Charles Wilson" , Subject: Re: Missing wide character functions in libc.a Date: Tue, 11 Sep 2001 18:19:00 -0000 Message-id: <008101c13b29$0a0fcc70$150a0eca@ewok> References: <006201c13a52$0627de90$150a0eca@ewok> <20010910195404.C18481@redhat.com> <3B9D67E3.70203@ece.gatech.edu> X-SW-Source: 2001-09/msg00603.html Would you know where can I find the source code to fix missing functions (wcspbrk(), wcschr(), wcsrchr(), wcscoll(), wcsrfxm(), towupper(), towlower() etc) in /lib/libc.a? I tried to "brower" from GNU's glibc source (which does not build on Cygwin at moment), but it does not seem to be a clean and easy cut. I also download Cygwin source, but seem to me that these function just haven't been implemented?! Thanks. Cheers, Herbert -- Preston Aviation Solution 488 Victoria Street, Richmond 3121 Tel: (03) 9426-8239 Email: herbert@preston.net ----- Original Message ----- From: "Charles Wilson" To: Cc: "Herbert" Sent: Tuesday, September 11, 2001 11:24 AM Subject: Re: Missing wide character functions in libc.a > BTW, this subject (wide and multibyte character functions in cygwin) > just came up on the XEmacs-nt list. Ben Wing is trying to get "MULE" > support for XEmacs to work on cygwin (MULE is some sort of > character-coding, wide-char, unicode thingy...) > > Anyway, check the xemacs-nt mailing list if you're interested: > http://list-archive.xemacs.org/xemacs-nt/ > > (Also, you may see references to a possible (new) bug in sscanf -- I > haven't had time to track that one down, and forgot to mention it. I'll > put that in its own thread) > > (Chris hates these taglines, but here goes: > Just a datapoint. > > --Chuck > > Hmm...the message I was referring to doesn't seem to have made it into > the xemacs-nt archives. Well, here it is from my local copy: > > > Ben Wing wrote: > > Mostly I've done a bunch of cleanup work. I also fixed the various bugs pointed > > out by Fabrice, Daniel Pittman, and others, although not yet Matej's, which are > > harder. It definitely should work on Windows w/Mule [probably without as well], > > and Cygwin w/o Mule. Probably on other platforms as well. One problem I've > > noticed so far is with Cygwin w/Mule: you get a crash at startup in > > parse-unicode-translation-table. I don't quite know what the problem is and > > haven't been able to debug it yet, as the debugger keeps locking up. > > > David A. Cobb responded. > > Ben, I trust you are aware that widechar & mbchar support in Cygwin is full of holes? > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/