This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: [RFC] 1.7 Packaging: Toolchain
On Jul 24 15:24, Christopher Faylor wrote:
> On Thu, Jul 24, 2008 at 03:53:16AM -0700, Brian Dessent wrote:
> >Corinna Vinschen wrote:
> >
> >> I don't know if that's a problem for std::wstring, but newlib is still
> >> missing the wprintf family of functions.
> >
> >Based on the defintion of GLIBCXX_ENABLE_WCHAR_T in
> ><http://gcc.gnu.org/viewcvs/trunk/libstdc%2B%2B-v3/acinclude.m4?view=markup>
> >the list of missing functions before wchar_t can be enabled is:
> >
> >fgetwc
> >fgetws
> >fputwc
> >fputws
> >fwide
> >fwprintf
> >fwscanf
> >getwc
> >getwchar
> >putwc
> >putwchar
> >swprintf
> >swscanf
> >ungetwc
> >vfwprintf
> >vswprintf
> >vwprintf
> >wcsftime
> >wcstod
> >wcstok
> >wprintf
> >wscanf
>
> Huh. That list is actually smaller than I would have expected.
>
> Can't we get all of these from freebsd?
Basically, yes, but not quite. At least the put/get functions and the
fwide function requires integration into the newlib stdio structures and
REENT support. It's not just a simple drop-in job.
> How about scrapping newlib in favor of freebsd libraries? I have been
> suggesting this for years. Maybe the timing is wrong since we want to
> release Cygwin ASAP but it sure would be nice to be in control of 100%
> of Cygwin and not have to wander over to newlib whenever we need to make
> changes.
If we had more man power, maybe. As it is, I see no chance. We also
talked about getting the above functions into newlib a few months ago on
cygwin-developers. Exactly nada happened so far. As far as I'm
concerned I'm glad that there's at least the libc part we only have to
marginally care about. Maybe that's something for 1.9.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat