On 07/17/2012 11:07 AM, gilles.chara...@charabot-org.fr wrote: >>> and make install to install Autoconf2.62 and I have success in this >> >> Why 2.62 and not 2.69? >> I have tried many of them 2.69 and 2.68 and 2.62 and this is the same > probleme,
That should be your hint that the problem is not in autoconf, but in your setup. >>> >>> And when I type autoconf -V on my terminal, I see >>> >>> autoconf (GNU Autoconf) 2.59 But if you type '/usr/local/bin/autoconf -V', you should get the just-installed version. That is, your PATH is requesting that 'autoconf' forwards to '/usr/bin/autoconf', and you did not replace that file when installing your self-built version. >> >> Based on what you said above, you successfully installed into >> /usr/local/bin, but your shell is probably still set to either have >> /usr/bin first in $PATH, > My bash shell have a $PATH with > /usr/bin before /usr/local/bin Yep, that is indeed your problem. Your setup is atypical (most distros stick /usr/local/bin/ before /usr/bin/ in their default setup of $PATH, so you must have customized things differently). You can also force your self-built versions to install into /usr/bin instead of /usr/local/bin by passing appropriate options to ./configure, although I would not recommend doing that (as it tends to make getting support from your distro much more difficult). > or else your shell has hashed the previous >> location of automake > > I never had automake before because no automake software was in this > computer > and at this time no automake yet. Apologies for my typo, I meant autoconf. But the point remains: it is your atypical choice of PATH that is letting a path lookup for autoconf find your old distro version instead of your just-built version, and if you want to find your just-built version without an absolute file name, then you need to fix your PATH. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
