Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 20100 invoked by uid 500); 3 Apr 2000 14:02:28 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 20087 invoked from network); 3 Apr 2000 14:02:27 -0000 Date: Mon, 3 Apr 2000 10:02:16 -0400 Message-Id: <200004031402.KAA13944@k5.localdomain> X-Authentication-Warning: k5.localdomain: trawick set sender to trawickj@bellsouth.net using -f From: Jeff Trawick To: new-httpd@apache.org In-reply-to: <200004031316.HAA12780@sanitas> (pg@sweng.stortek.com) Subject: Re: using perl in the configuration process Reply-to: trawickj@bellsouth.net References: <200004031316.HAA12780@sanitas> X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I certainly prefer installing perl on OS/390 than autoconf/m4/libtool whatever. Also, perl actually works on OS/390, whereas libtool doesn't. We've been using the Mortice Kern port of autoconf with Apache 2.0 on OS/390 and haven't had many problems with autoconf so far. I found an ASCII-ism in an autoconf-provided test which supposedly sees if you have ANSI header files, but I don't remember any other autoconf problems. There are more config issues yet to solve so there is room for more autoconf snafus, but so far so good. Ryan raised the issue of licensing over the weekend; that is my main concern. Note that Apache won't currently build on all supported platforms if GPL-ed code were removed. -- Jeff Trawick | trawick@ibm.net | PGP public key at web site: http://www.geocities.com/SiliconValley/Park/9289/ Born in Roswell... married an alien...