Jump to content

Autoconf 2.61 or higher


Guest tendonsie

Recommended Posts

I use more than one year mangos and compile works great.

I use Centos 5.4.

Now today, I want to update my MaNGOS and I compile I have next problem:

configure.ac:39: error: Autoconf version 2.61 or higher is requierd.
configure.ac:39: the top level
and then erorr error error and it stops.

Now I have autoconf 2.59 on my Centos 5.4.

I upgrade it:

yum update autoconf

Feedback: no packages marked for update. Nothing to update.

So i decedid to upgrade to Centos 5.5.

Now I got Centos 5.5 (Final)

Again try to compile MaNGOS, again it don't work.

With yum update the same like before.

Any idea what to do? Centos don't see i higher autoconf version then I have now, but for mangos I need higher one.

Thanks.

Link to comment
Share on other sites

Just do the following

--- a/dep/ACE_wrappers/configure.ac     2010-10-30 17:36:27.000000000 +0400
+++ b/dep/ACE_wrappers/configure.ac     2010-10-30 17:37:19.000000000 +0400
@@ -36,7 +36,7 @@

dnl Require GNU Autoconf 2.58 or better.  Previous versions did not
dnl correctly support HP-UX.
-AC_PREREQ(2.61)
+AC_PREREQ(2.59)

dnl Autoconf explicitly forbids patterns containing "_AC_".  This causes
dnl a problem when using MPC to generate the Automake ".am" files since

And it will do with 2.59. Don't know why it was bumped to 2.61. Tested, configures and builds without a scratch on CentOS.

Link to comment
Share on other sites

dep/ACE_wrappers/configure.ac

@@ -39,7 +36,7 @@ additional details.])

dnl Require GNU Autoconf 2.58 or better.  Previous versions did not
dnl correctly support HP-UX.
-AC_PREREQ([2.58])
+AC_PREREQ(2.61)

dnl Autoconf explicitly forbids patterns containing "_AC_".  This causes
dnl a problem when using MPC to generate the Automake ".am" files since

3c0f8c0efca89 , the ACE update commit by Neo2003. Maybe the reason can be found in ACE scm logs.

Link to comment
Share on other sites

  • 2 weeks later...
There must be some reason though, I doubt they would up the requirement just because a new version was released.

There is no errors in autoconf run, so we may assume this requirement is void in our case.

Well... soon is CentOS 6 coming, so we won't need this small fix anymore :)

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use