Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <036401c0ff5c$a01552c0$806410ac@local> From: "Robert Collins" To: "John Wiersba" , References: <03F4742D8225D21191EF00805FE62B9908E23EDD AT aa-msg-01 DOT medstat DOT com> Subject: Re: "shouted down", "shot down", apologies Date: Thu, 28 Jun 2001 08:58:04 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-OriginalArrivalTime: 27 Jun 2001 22:48:21.0523 (UTC) FILETIME=[440DB630:01C0FF5B] ----- Original Message ----- From: "John Wiersba" > Well, what I'd like to do, and what should be standard for any package > accepted into the cygwin archive (available to be downloaded with > setup.exe), is that each package source tarball should build out-of-the-box > under cygwin with a simple make configure; make; make test (check?); make > install, including the most recent "stable" cygwin source tarball. With a For everything but cygwin1.dll, that _should_ work. Us maintainers put pre-patched source (if cygwin patches are needed) into the src tarball. Have you tried? If you've tried and a package didn't work, report a bug to the maintainer - they will take it seriously. If you're asking a hyopthetical "have the cygwin package maintainers done the obvious thing" then I think you're wasting my time. Some packages such as cygwin1.dll and gcc _WILL NOT_ build in the same directory as the source. For them you need mkdir pkgdir cd pkgdir tar xzf /path/to/tarball mkdir obj cd obj ../extractedpackagesrc/configure make Hope that answers the question. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/