Hi,

I've switched to Gentoo recently (bootstrap from stage1) and experienced problems with autoconf, which would reject a configure.in script of mine that worked before. It almost seemed to me as if things had changed back to the way they were in much earlier autoconf versions... now I checked if it may actually be the case that autoconf is outdated, so I did:

$ etcat -v autoconf
[ Results for search key           : autoconf ]
[ Candidate applications found : 4 ]

Only printing found installed programs.

*  sys-devel/autoconf-2.57-r1 :
       [   ] 2.57-r1 (2.5)

*  sys-devel/autoconf-2.57a-r1 :
       [M~ ] 2.57a-r1 (2.5)

*  sys-devel/autoconf-2.58 :
       [  I] 2.58 (2.5)

*  sys-devel/autoconf-2.59 :
       [M~ ] 2.59 (2.5)


Ok, so etcat says I have autoconf 2.58 installed, which so far is the latest unmasked version. However, when I do "autoconf --version", it says:


Autoconf version 2.13

which is ancient! Also, the info pages seem to belong to an autoconf much older than 2.58. "qpkg -f `which autoconf`" says sys-devel/autoconf.
I now found out that autoconf-2.58 actually installs *two* versions, namely 2.13 and 2.58, to be invoked by "autoconf-(versionno.)" (and the more recent
info pages are accessed with "info autoconf25"), so I would like to know:


- Why are the two versions not in two separate packages, and accordingly displayed by etcat?
- Why does "autoconf" by default invoke the older version?
- How can I change the default to autoconf 2.58? Will my system survive this? ;-} /usr/bin/autoconf is a symlink pointing to ../lib/autoconf/ac-wrapper.pl



-- [EMAIL PROTECTED] mailing list



Reply via email to