Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Date: Fri, 24 May 2002 17:16:51 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <83513187704.20020524171651@logos-m.ru> To: "Conrad Scott" CC: cygwin-developers AT cygwin DOT com Subject: Re: has anyone run the test suite recently? In-Reply-To: <00d701c20319$8c617c60$6132bc3e@BABEL> References: <00d701c20319$8c617c60$6132bc3e AT BABEL> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Friday, 24 May, 2002 Conrad Scott Conrad DOT Scott AT dsl DOT pipex DOT com wrote: CS> "Conrad Scott" wibbled: CS>> I did notice that if I compiled cygwin (i.e. the dll and so forth) with CS>> the current release (1.3.10-1) installed on my machine, I got a sequence of CS>> problems with the tests. But if I installed a newly built copy of cygwin CS>> and *then* re-built and re-tested the same source tree, it all passed fine. CS>> I'll try this again and preserve some log files. CS> Having decided to think about what I wrote (perhaps I'll get the hang of CS> doing this *before* I post one day), I assume that 'make check' is really a CS> post-install test as otherwise it can't use the newly built dll. Thus one CS> would rather expect some test failures if it was done before installation CS> (as I might have been trying . . .). Actually, testsuite is supposed to test not yet installed new-cygwin1.dll. If you take a look at Makefiles and testsuite scripts, you'll see that all tests are linked with special import library, which makes them use new-cygwin1.dll instead of cygwin1.dll and are run via cygrun so they don't interfere with other running cygwin processes. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19