From owner-freebsd-questions@FreeBSD.ORG Sat Feb 7 09:26:42 2004 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 1310A16A4CE for ; Sat, 7 Feb 2004 09:26:42 -0800 (PST) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id D16A943D1F for ; Sat, 7 Feb 2004 09:26:41 -0800 (PST) (envelope-from jshamlet@comcast.net) Received: from hades (pcp04637401pcs.gambrl01.md.comcast.net[68.49.84.210]) by comcast.net (sccrmhc12) with SMTP id <20040207172641012007vec2e>; Sat, 7 Feb 2004 17:26:41 +0000 From: "J. Seth Henry" To: freebsd-questions@freebsd.org Date: Sat, 7 Feb 2004 12:27:47 -0500 User-Agent: KMail/1.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402071227.47388.jshamlet@comcast.net> Subject: Autoconf 2.57 upgrade oddities - files all have '257 suffix. 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: Sat, 07 Feb 2004 17:26:42 -0000 Guys, I discovered this while attempting to upgrade to KDE 3.2.0 on my FreeBSD 4.9-REL box last night. Unfortunately, kdevelop 3 won't build because of a problem with autoconf. When I first started the upgrade, I apparently had 2.53_1 installed, so it complained that it needs 2.54 or later. I tried manually updating autoconf alone, and portupgrade went through the motions, but when it finished, 2.53_1 was still there and 2.57_1 wasn't. I then tried manually deinstalling 2.53_1, and manually installing 2.57_1. This seemed to work, but now I don't have an autoconf anywhere! (the program isn't on the disk- I even tried find / -name autoconf) Now, here's the interesting part. I dig around and find that the binary IS on the hard disk, but all of the autoconf binaries have a '257' suffix. (ie autoconf257) I sym-link all of the binaries to their generic names, and things seem to be working? So, at the moment, I have the following, and things seem to be working. alexandria# ls -l /usr/local/bin | grep 257 lrwxr-xr-x 1 root wheel 11 Feb 7 12:15 autoconf -> autoconf257 -r-xr-xr-x 1 root wheel 7684 Feb 2 23:43 autoconf257 lrwxr-xr-x 1 root wheel 13 Feb 7 12:16 autoheader -> autoheader257 -r-xr-xr-x 1 root wheel 7959 Feb 2 23:43 autoheader257 lrwxr-xr-x 1 root wheel 11 Feb 7 12:19 autom4te -> autom4te257 -r-xr-xr-x 1 root wheel 33557 Feb 2 23:43 autom4te257 lrwxr-xr-x 1 root wheel 13 Feb 7 12:19 autoreconf -> autoreconf257 -r-xr-xr-x 1 root wheel 17612 Feb 2 23:43 autoreconf257 lrwxr-xr-x 1 root wheel 11 Feb 7 12:19 autoscan -> autoscan257 -r-xr-xr-x 1 root wheel 16060 Feb 2 23:43 autoscan257 lrwxr-xr-x 1 root wheel 13 Feb 7 12:19 autoupdate -> autoupdate257 -r-xr-xr-x 1 root wheel 32888 Feb 2 23:43 autoupdate257 lrwxr-xr-x 1 root wheel 10 Feb 7 12:19 ifnames -> ifnames257 -r-xr-xr-x 1 root wheel 3607 Feb 2 23:43 ifnames257 Is this a bug, or did I screw up something? Thanks, Seth Henry