From rbb@covalent.net Fri Jan 5 19:08:57 2001 Return-Path: Mailing-List: contact cvs-help@apr.apache.org; run by ezmlm Delivered-To: mailing list cvs@apr.apache.org Received: (qmail 78676 invoked from network); 5 Jan 2001 19:08:57 -0000 Received: from sfo-gw.covalent.net (HELO koj.covalent.net) (207.44.198.62) by h31.sny.collab.net with SMTP; 5 Jan 2001 19:08:57 -0000 Received: from rbb (helo=localhost) by koj.covalent.net with local-esmtp (Exim 3.16 #1) id 14EcHm-0000Y9-00; Fri, 05 Jan 2001 11:12:22 -0800 Date: Fri, 5 Jan 2001 11:12:22 -0800 (PST) From: rbb@covalent.net X-Sender: rbb@koj To: dev@apr.apache.org cc: apr-cvs@apache.org Subject: Re: cvs commit: apr configure.in In-Reply-To: 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 > > 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? Sounds good. Or, we could just check to see if we are on linux and sendfile is defined. Is that a good enough check? Ryan _______________________________________________________________________________ Ryan Bloom rbb@apache.org 406 29th St. San Francisco, CA 94131 -------------------------------------------------------------------------------