Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>, <newlib AT sources DOT redhat DOT com>
Subject:	Testing newlib under cygwin
Date:	Thu, 7 Apr 2005 19:47:21 +0100
MIME-Version:	1.0
Message-ID:	<SERRANOCj1d4vJFRFWM000000a9@SERRANO.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	07 Apr 2005 18:47:24.0066 (UTC) FILETIME=[3CCBD820:01C53BA2]

    Hi folks,


  ISTM that when I run "make check-target-newlib" in my cygwin build tree,
what actually gets tested is the newlib that's linked into the
currently-installed version of the cygwin1 dll.  

  This isn't entirely unexpected of course, but what I was wondering is,
given that the cygwin testsuite is set up to use the newly-compiled cygwin
dll, is there any convenient way to run the newlib testsuite using the new
cygwin dll rather than the installed one?  Or to run the testsuite apps
statically linked against the newly built newlib lib?.a files?



    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/

- Raw text -