On Mon, 30 Dec 2002 10:51:10 +0100 Sebastian Geerken <s.geerken@ping.de> wrote:
On Mon, Dec 30, Sebastian Geerken wrote:
On Sun, Dec 29, Eric GAUDET wrote:
I had the same problem with autoconf v2.13. I updated to 2.54, and I don't see this problem anymore.
If you have installed both versions (at least in debian, "autoconf" 2.53 depends on "autoconf2.13"?), call "autconf2.50" explicitely, before "./configure". There seems to be something wrong with, perhaps with the timestamps?
The timestamp is of course the one of the checkout time, so I have:
-rwxr-xr-x 1 sg sg 165570 Dec 30 10:46 configure -rw-r--r-- 1 sg sg 4389 Dec 30 10:46 configure.in
"make" will then create again "configure", but uses autoconf 2.13, instead of 2.5x. Does someone know autoconf well enough to get it starting a specific version?
Sebastian
Hi there Sebastian (and the rest). After realising that autoconf > 2.13 was required, I also realised that on my mandrake both are actually installed, with a script linked to /usr/bin/autoconf . The trick with this script was to export the environment needed to use the higher version, and on my mandrake the trick was to first "export WANT_AUTOCONF_2_5=1" .. then the rest. I'm not sure if this is standard on other recent distros, but after exporting this environment, configuring and compiling works great ;-) Maybe this helps ;-) Greetings Ralph -- http://tuxpower.f2g.net/ http://axljab.homelinux.org:8080/ "I have opinions of my own, strong opinions, but I don't always agree with them." -- George H. W. Bush