From owner-freebsd-questions@FreeBSD.ORG Thu Jun 9 16:27:49 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 462CA16A41C for ; Thu, 9 Jun 2005 16:27:49 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01A8443D4C for ; Thu, 9 Jun 2005 16:27:48 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id j59GRe6v011770; Thu, 9 Jun 2005 11:27:40 -0500 (CDT) (envelope-from dan) Date: Thu, 9 Jun 2005 11:27:40 -0500 From: Dan Nelson To: Giorgos Keramidas Message-ID: <20050609162739.GC2836@dan.emsphone.com> References: <20050609110039.N71755@mail.goinet.com> <20050609161145.GA70744@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050609161145.GA70744@orion.daedalusnetworks.priv> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.9i Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade, automake14 -> automake19 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jun 2005 16:27:49 -0000 In the last episode (Jun 09), Giorgos Keramidas said: > On 2005-06-09 11:01, Tony Shadwick wrote: > > Could someone give me a quick hint on switching from automake14 to > > automake19 using the ports tree without wreaking total havock on > > dependencies? :) > > If you are asking what portupgrade will do with the installed ports, > then there's nothing to worry about. Just run portupgrade -a and it > will take care of building the necessary auto* ports too. > > If you are using automake14 in software you write or build yourself > outside of the Ports tree, don't. For an example of what may go > wrong, see the misc/81558 problem report: I have never had problems using the numbered auto* ports when building programs from CVS trees. Here's the bootstrap script I use: it also works great on Debian and RedHat, which ship numbered auto* binaries as well. #!/bin/sh -e # Run this to update & generate all the automatic things # # Some OSes (RedHat) symlink 'autoconf' to 2.13 even though a perfectly # good 2.5x is available. If a numbered version is not found, the # non-numbered executable will be used, and we hope for the best. AC= for i in 259 -2.59 258 -2.58 257 -2.57 256 -2.56 255 -2.55 2.55 254 -2.54 2.54 253 -2.53 2.53 ; do if type autoconf$i >/dev/null 2>&1 ; then AC=$i ; echo detected autoconf$AC ; break fi done AM= for i in 19 -1.9 18 -1.8 17 -1.7 1.6 -1.6 15 -1.5 ; do if type automake$i >/dev/null 2>&1 ; then AM=$i ; echo detected automake$AM ; break fi done # export these because all 5 need to know the exact name of the other ones AUTOCONF=autoconf$AC ; export AUTOCONF AUTOHEADER=autoheader$AC ; export AUTOHEADER AUTOM4TE=autom4te$AC ; export AUTOM4TE ACLOCAL=aclocal$AM ; export ACLOCAL AUTOMAKE=automake$AM ; export AUTOMAKE rm -rf autom4te* $ACLOCAL -I . $AUTOHEADER $AUTOMAKE --add-missing $AUTOCONF -- Dan Nelson dnelson@allantgroup.com