Date: Sat, 7 Feb 2004 10:36:08 -0800 From: Kent Stewart <kstewart@owt.com> To: freebsd-questions@freebsd.org Cc: "J. Seth Henry" <jshamlet@comcast.net> Subject: Re: Autoconf 2.57 upgrade oddities - files all have '257 suffix. Message-ID: <200402071036.08707.kstewart@owt.com> In-Reply-To: <200402071227.47388.jshamlet@comcast.net> References: <200402071227.47388.jshamlet@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 07 February 2004 09:27 am, J. Seth Henry wrote: > 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? Kdevelop will build just fine but it produces a message. You have to have cvsuped ports-all after 0930 UTC to get the changes to kdevelop that will make it build. The changes were available from my cvsup mirror around 1020 UTC on 7 Feb 2003. Kdesdk had a problem with pod2man. It needed to use the pod2man from Perl 5.6.1 but use.perl port doesn't create the links in /usr/bin/pod2* > /usr/local/bin/pod2*. The changes to bypass building the man pages were available on your local cvsup-mirror after 1400 UTC. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402071036.08707.kstewart>