X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <4A0EA4BD.4010703@gmail.com> Date: Sat, 16 May 2009 12:34:21 +0100 From: Dave Korn User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: managing autoconf versions? References: <1242445850 DOT 26068 DOT ezmlm AT cygwin DOT com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Jay wrote: > This is a little off topic. > > How do people manage autoconf/automake versions? > GCC/binutils require specialised versions, and I keep them in a separate prefix, thanks to Chuck's gcc-tools-* packages, and add them to the front of $PATH when needed. For all other stuff, the automake/autoconf wrapper scripts that are part of the standard distro versions suffice to select a suitably-near match, at least in my experience. cheers, DaveK -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/