Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20041012174207.26685.qmail@web41504.mail.yahoo.com> X-RocketYMMF: kelleycook Date: Tue, 12 Oct 2004 10:42:06 -0700 (PDT) From: Kelley Cook Reply-To: kcook AT gcc DOT gnu DOT org Subject: Re: [toplevel, Cygwin] Don't warn if both newlib and winsup are missing To: Zack Weinberg , Kelley Cook , Dave Korn Cc: cygwin AT sources DOT redhat DOT com, gcc-patches AT gcc DOT gnu DOT org In-Reply-To: <87y8ibu9wf.fsf@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- 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 -- 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/