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 Message-ID: <001001c21afa$8123fa00$6132bc3e@BABEL> From: "Conrad Scott" To: Cc: "Gerrit P. Haase" Subject: Release of the and files Date: Sun, 23 Jun 2002 22:11:11 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In the upcoming release of cygwin, is it possible to exclude the and files from the distribution? Gerrit Haase pointed out to me that the perl-5.8.0 configuration script generates "entry point not found" errors (in one of those dratted dialogue boxes) for shmat(2) under current snapshots, since it successfully compiles a test program, against the header, and then tries to run it, with the predictable result (AFAICT: ever tried reading a Larry Wall-style configure script?). I can't see how any configure script can easily avoid such noise under the current arrangement and worse, it might do no more than compile a test file, and not run it too, and so configure the software to use shared memory. Is there any difficulty with excluding these files? or, am I behind the times and this is already the intention? There is some discussion of this in http://sources.redhat.com/ml/cygwin-developers/2002-03/msg00010.html but it's not clear what the final result of this was (except that the header files are still in the snapshot). // Conrad