Re: cygwin not respecting --without-newlib?

[Christopher Faylor <cgf at redhat dot com>]

On Tue, Jul 09, 2002 at 02:15:44PM -0400, Nathanael Nerode wrote:
>On Tue, Jul 09, 2002 at 02:06:31PM -0400, DJ Delorie wrote:
>> 
>> Cygwin *is* newlib.  When you build the cygwin DLL (cygwin1.dll) it
>> directly incorporates the newlib objects into it.  So, you must always
>> build newlib when you're building cygwin, and anything built for
>> cygwin is being built for newlib.
>
>OK; I'm not sure this helps me. :-)
>
>Suppose you're building a combined tree targeting Cygwin.  What should
>it mean to specify --without-newlib?  
>
>Should it mean "Don't build or use the newlib in the tree: use the
>preinstalled Cygwin libraries, or the ones I specified with --with-libs
>and --with-headers"?
>
>Should it simply be illegal, and result in an error message?

If there is a newlib in the tree, cygwin will attempt to use it.  Hence,
--without-newlib should be illegal for a cygwin target.

cgf