Subject: RE: [toplevel, Cygwin] Don't warn if both newlib and winsup are missing
From: "Dave Korn" <[email-masked]>
To: <[email-masked]>, "'Zack Weinberg'" <[email-masked]>
Cc: <[email-masked]>, <[email-masked]>
Date: Tue, 12 Oct 2004 18:53:05 +0100

> -----Original Message-----
> From: Kelley Cook 
> Sent: 12 October 2004 18:42

> --- Zack Weinberg wrote:
> 
> > Kelley Cook writes:
> > 
> >> In July a patch was added to the Cygwin's toplevel that turns off
> >> newlib if winsup isn't also present.
> > 
> > Hang on, is this even the right thing?  Aren't there 
> embedded targets
> > that use newlib but not winsup?
> 
> Sure there are.
> 
> But this hunk of configure code only applied to target *-*-cygwin*,
> which will not build newlib without winsup.
> 
> See http://gcc.gnu.org/ml/gcc-patches/2004-06/msg01388.html for when
> this was added.
> 
> KC

  This is a very strange way round to express the dependencies if you ask
me.

  Cygwin depends on winsup, winsup depends on newlib.  Well, I guess if
newlib won't build in cygwin configuration without winsup being present then
I guess its a circular dependency.  Still sounds a bit strange to me though.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/