Return-Path: Mailing-List: contact cvs-help@apr.apache.org; run by ezmlm Delivered-To: mailing list cvs@apr.apache.org Received: (qmail 77494 invoked from network); 5 Jan 2001 19:04:01 -0000 Received: from polz.de (HELO sockratte.schell.de) (195.20.238.74) by h31.sny.collab.net with SMTP; 5 Jan 2001 19:04:01 -0000 Received: (qmail 25590 invoked from network); 5 Jan 2001 19:04:02 -0000 Received: from unknown (HELO rossini.schumann.cx) (217.1.190.193) by polz.de with SMTP; 5 Jan 2001 19:04:02 -0000 Received: from localhost (localhost [127.0.0.1]) by rossini.schumann.cx (Postfix) with ESMTP id 531235E007; Fri, 5 Jan 2001 19:59:15 +0100 (CET) Date: Fri, 5 Jan 2001 19:59:15 +0100 (CET) From: Sascha Schumann X-Sender: To: Cc: Subject: Re: cvs commit: apr configure.in In-Reply-To: <20010105171958.77185.qmail@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N On 5 Jan 2001 rbb@apache.org wrote: > rbb 01/01/05 09:19:57 > > Modified: . configure.in > Log: > Some Linux's do not define TCP_CORK. I guess you are referring to libc 5.x.x systems? There are still kernels around (2.0.x, early 2.2.x possibly) which don't support TCP_CORK, so I think we should not simply presume that TCP_CORK works. Would anyone mind, if the *linux* portion of the case statement would egrep linux/socket.h for TCP_CORK? - Sascha