This is the mail archive of the
newlib@sources.redhat.com
mailing list for the newlib project.
Re: Newlib resolver [was Re: minires-0.95 - a new package ready for review]
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: newlib at sources dot redhat dot com
- Date: Fri, 13 Jun 2003 09:22:32 +0200
- Subject: Re: Newlib resolver [was Re: minires-0.95 - a new package ready for review]
- References: <fzmgbbqo.fsf@blue.sea.net> <Pine.CYG.4.55.0306112147580.3944@ellixia> <Pine.CYG.4.55.0306112222530.3944@ellixia> <3EE7E680.9080102@netscape.net> <20030612031509.GA8714@redhat.com> <3EE8A108.EC1238B3@ieee.org> <20030612173051.GH19331@redhat.com> <3EE8DAC7.5050705@netscape.net> <3EE90C23.8060606@redhat.com>
- Reply-to: newlib at sources dot redhat dot com
On Thu, Jun 12, 2003 at 07:26:27PM -0400, J. Johnston wrote:
> From the sounds of it, it belongs in winsup because it uses Windows APIs.
> Corinna
> has already removed the newlib/libc/sys/cygwin directory from newlib.
That's just a minor part of the story. It uses *one* function from the
Windows API which is used if /etc/resolve.conf is not available.
All the rest of minires is using pure socket functionality and therefore
just a tiny part of the lib is actually Windows dependent. Even on Windows,
a resolve.conf overwrites using the Windows API.
So this has nothing to do with Cygwin in the first place. Minires
would add a resolver lib to newlib which is 99% platform independent
and the 1% Windows API could be appropriately ifdef'd out.
Does that sound different now?
Corinna
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com