Return-Path: Delivered-To: new-httpd-archive@hyperreal.org Received: (qmail 16959 invoked by uid 6000); 5 Mar 1998 10:48:59 -0000 Received: (qmail 16950 invoked from network); 5 Mar 1998 10:48:55 -0000 Received: from slarti.muc.de (193.174.4.10) by taz.hyperreal.org with SMTP; 5 Mar 1998 10:48:55 -0000 Received: (qmail 11467 invoked by uid 66); 5 Mar 1998 10:48:48 -0000 Received: by en1.engelschall.com (Sendmail 8.8.8) for new-httpd@apache.org id LAA06433; Thu, 5 Mar 1998 11:39:00 +0100 (MET) Message-Id: <199803051039.LAA06433@en1.engelschall.com> Subject: Re: #define collisions To: new-httpd@apache.org Date: Thu, 5 Mar 1998 11:39:00 +0100 (MET) From: rse@engelschall.com (Ralf S. Engelschall) Organization: Engelschall, Germany. X-Home: http://www.engelschall.com/ X-Mailer: ELM [version 2.4ME+ PL39 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org In article you wrote: > Isn't any module using autoconf practically guaranteeing a conflict with > anything else using autoconf? Not in general. As long as all packages use the _SAME_ autoconf defines this is no problem. In other words: Using just the pre-defined autoconf stuff makes usually no problems. But custom defines can conflict, of course. In case of Rasmus' HAVE_CRYPT_H this should be no problem. Because per convention this means is available for #include. So what exactly is the problem for you, Rasmus, when Apache says HAVE_CRYPT_H? >> Well, we knew this was coming. Now that I am including the Apache header >> files with all the appropriate -D's set, I am hitting a couple of >> collisions. HAVE_CRYPT_H from conf.h, for example. Is there some logic >> behind using autoconf-style #define's here? Aren't we pretty much >> guaranteeing clashes with any module using autoconf by doing this? Ralf S. Engelschall rse@engelschall.com www.engelschall.com