This is the mail archive of the
mailing list for the Cygwin project.
RE: help: Glib under Cygwin
- To: <cygwin at cygwin dot com>
- Subject: RE: help: Glib under Cygwin
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Tue, 17 Apr 2001 12:39:30 +1000
- Thread-Index: AcDG4jU/DftaV6OXQ56a+Ct/gQ3sWAABILUw
- Thread-Topic: help: Glib under Cygwin
> -----Original Message-----
> From: Christopher Faylor [mailto:email@example.com]
> Sent: Tuesday, April 17, 2001 12:08 PM
> To: firstname.lastname@example.org
> Subject: Re: help: Glib under Cygwin
> >I have enough problems without needing to swim against that
> sort of current.
> Um, yeah, Ulrich is not a Windows lover, to put it mildly.
> He's hardly alone
> at Red Hat, though.
> I wasn't around during Cygwin's inception but I believe that Cygwin
> actually exists because Ulrich was adamant about not porting glibc to
That would only impact newlib surely? I mean, AFAIK, if glibc was ported
wouldn't large chunks of cygwin still be essential? (Console handlers,
pipes, sockets, file io, threads, win32 security mapping just for
> However, aren't we talking about 'glib' not 'glibc'?
I think David was mislead by one of the early posters jump from glib to
glibc. And David then went to do the "right thing" by cygwin, and got
jumped on. This sort of negative feedback isn't very beneficial....
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple