From owner-freebsd-questions@FreeBSD.ORG Thu Mar 3 04:16:26 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B64C16A4CF for ; Thu, 3 Mar 2005 04:16:26 +0000 (GMT) Received: from mail.codesourcery.com (admin.voldemort.codesourcery.com [65.74.133.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 241DE43D1D for ; Thu, 3 Mar 2005 04:16:26 +0000 (GMT) (envelope-from seefeld@sympatico.ca) Received: (qmail 9078 invoked from network); 3 Mar 2005 04:16:25 -0000 Received: from localhost (HELO ?192.168.0.101?) (stefan@127.0.0.1) by mail.codesourcery.com with SMTP; 3 Mar 2005 04:16:25 -0000 Message-ID: <42268F70.7070208@sympatico.ca> Date: Wed, 02 Mar 2005 23:15:44 -0500 From: Stefan Seefeld User-Agent: Mozilla Thunderbird 0.9 (X11/20041127) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <4226862E.30403@sympatico.ca> <20050303034141.GA89476@xor.obsecurity.org> In-Reply-To: <20050303034141.GA89476@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: where is autoconf X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 04:16:26 -0000 Kris Kennaway wrote: >>Well, I was looking for 'autoconf' in these files but didn't find it. >>And indeed, even though I have 'autoconf-2.59_2' installed, all I have >>is 'autoconf259', but not 'autoconf'. > > > This is necessary because the autoconf developers don't understand why > backwards compatibility is important for their tools (new versions > like 2.59 cannot be used to build old applications that were written > for e.g. 2.13, nor can multiple versions of autoconf be easily > installed concurrently). I'm aware of these (very unfortunate) incompatibilities, though I had expected the problem to be dealt with differently (for example by setting a symbolic link to the currently active version). > You can use the gnu-autoconf and related ports, which installs into > /usr/local/gnu-autotools so they do not poison the build environment > of other ports. YOu might have to play games with PATH or other > variables to get your application to find them. Ok, thanks for the explanation. Regards, Stefan