Contact Us

Home > Error This > Error This File Was Generated For Autoconf 2.61

Error This File Was Generated For Autoconf 2.61

Special case: KDE packages using kde.eclass While KDE 3.x uses autotools like many other software packages, it is using a custom setup for them, with lots of custom macros, and further Common failure cases and causes Possibly undefined macros The most common failure with autotools is related to the autoconf message "possibly undefined macro: SOME_MACRO". yes checking for pj_init in -lproj... The contents of this document, unless otherwise expressly stated, are licensed under the CC-BY-SA-3.0 license. his comment is here

Sign in to comment Contact GitHub API Training Shop Blog About © 2016 GitHub, Inc. Missing dependencies' version Since about Summer 2006, automake and autoconf wrappers don't depend on all the versions of the respective packages forcefully, which means you cannot rely on the users to For this reason, those functions are preferred over manual call or broken or almost pointless custom scripts. Last modified: Fri Oct 14 21:28:19 2016; Machine Name: beach Debian Bug tracking system Copyright (C) 1999 Darren O. https://github.com/arangodb/arangodb/issues/630

You might have modified some files without having the proper tools for further handling them. The same goes if the package is not using automake but just autoconf . pass_all checking for ar...

The right way to solve this issue (to send upstream) is to add to the AUTOMAKE_OPTIONS variable the option foreign so that it will know to use foreign support out of Even worse, if the automake version used by the package is not installed (for instance if the package uses the old 1.8 version, while the user only has the last 1.10 yes checking whether to build static libraries... Privacy policy About Gentoo Wiki Disclaimers © 2001–2016 Gentoo Foundation, Inc.

no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking whether we are cross compiling... In these cases, automake will be invoked to just rebuild the involved Makefile.in , but it will work only if the autoconf version in the system is the same as the GNU/Linux ld.so checking how to hardcode library paths into programs...

yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... ACLOCAL_AMFLAGS = -I m4 ... Less often, but still happens, there are no directories with m4 files, or the files with the undefined macro isn't there; to solve this issue, you have to search for which Bruno reply via email to [Prev in Thread] Current Thread [Next in Thread] automatic update Makefile.am -> Makefile.in -> Makefile no longer working, Bruno Haible<= Re: automatic update Makefile.am -> Makefile.in

make[3]: Leaving directory `/build/libidn-0.6.14/gl' make[2]: Leaving directory `/build/libidn-0.6.14/gl' Making all in lib/gl make[2]: Entering directory `/build/libidn-0.6.14/lib/gl' cd ../.. && /bin/sh ./config.status lib/gl/Makefile depfiles config.status: creating lib/gl/Makefile config.status: executing depfiles commands make[2]: https://bugs.debian.org/542995 And since there are 3 current releases of autoconf (2.59, 2.60, 2.61), you have a 2/3 chance of failing this criterion. Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 218 Star 2,689 Fork 237 arangodb/arangodb Code Issues 171 Pull requests 4 Projects Message #5 received at [email protected] (full text, mbox, reply): From: Lucas Nussbaum To: [email protected] Subject: trilinos: FTBFS: aclocal.m4:14: error: this file was generated for autoconf 2.61.

Actual results: acsite.m4:6594: error: this file was generated for autoconf 2.61. this content You have another version of autoconf. yes checking for TIFFMergeFieldInfo in -ltiff... The Gentoo Name and Logo Usage Guidelines apply.

none checking for g++... a.out checking whether the C compiler works... This was removed from Debian last month. [1] It also build-depends on python-numpy, which is the suggested alternative. weblink yes checking if EPSG tables will be read from .csv files...

Regards Christoph -- /"\ ASCII Ribbon : GPG-Key ID: 0xD49AE731 \ / Campaign : CaCert Assurer X against HTML : Debian Maintainer / \ in eMails : http://www.debian.org/ http://www.christoph-egger.org/ Reply sent Your patch does build for me in both amd64 and i386 chroots so I'm currently preparing a NMU doing exactly that. CODE depending on autoconf 2.1 and automake 1.4WANT_AUTOCONF="2.1" WANT_AUTOMAKE="1.4" inherit autotools In many cases, instead of depending on a given version of automake or autoconf, we want to depend on the

x86_64-unknown-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F

Copy sent to Debian Scientific Computing Team . (Sat, 28 Nov 2009 15:42:05 GMT) Full text and rfc822 format available. This message is issued when a macro is called from the configure.ac or configure.in file but it's not defined in the aclocal.m4 file created by aclocal . aclocal.m4:17: the top level autom4te: /usr/bin/m4 failed with exit status: 63 autoheader: '/usr/local/bin/autom4te' failed with exit status: 63 make: *** [config.hin] Error 1 $ The distribution package was built with autoconf Debian Bug report logs - #542995 trilinos: FTBFS: aclocal.m4:14: error: this file was generated for autoconf 2.61.

Copy sent to Debian Scientific Computing Team . (Wed, 21 Oct 2009 06:03:03 GMT) Full text and rfc822 format available. If you want to use that, you should regenerate the build system entirely. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. http://vgadownload.com/error-this/error-this-movie-file-has-temporal-compression.html Index Nav: [DateIndex] [SubjectIndex] [AuthorIndex] [ThreadIndex] Message Nav: [DatePrev][DateNext] [ThreadPrev][ThreadNext] Other format: [Raw text] [patch] cygport-0.2.7 autoconf-2.61/automake-1.10 support From: Charles Wilson To: cygwin at

It's simple to recognize a package which build system is based on autotools: if there's a configure script, and a configure.in or configure.ac file, the build system is based on autoconf; g++ -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking whether the shell understands "+="... no checking dynamic linker characteristics...

This is solved by rebuilding autotools properly as described above, through the eautoreconf function (or other method depending on eventual higher level eclasses), instead of leaving maintainer mode to take care yes checking if g++ supports -c -o file.o... Macros written by developers for their software to be detected in the system by use of autotools are usually written in m4 files that are installed in the aforementioned /usr/share/aclocal directory. If you want to use that, you should regenerate the build system entirely.

This is not the case once a new autoconf version is released. Message #20 received at [email protected] (full text, mbox, reply): From: "Christophe Prud'homme" To: [email protected] Subject: Fixed in 10.0.3 upload Date: Mon, 21 Dec 2009 06:54:13 +0100 Hello, Trilinos 10 now The macro doesn't even involve any comparison, to my eye. autom4te will output the name of # the file in the diagnostic anyway. $output = "m4_if(m4_PACKAGE_VERSION, [$ac_version],, [m4_fatal([this file was generated for autoconf $ac_version.

For this reason,autoreconf is deprecated and avoided as possible (the same goes for custom upstream-provided scripts that uses it). This article is based on a document formerly found on our main website gentoo.org. Request was from Debbugs Internal Request to [email protected] (Mon, 18 Jan 2010 07:40:55 GMT) Full text and rfc822 format available. The following people contributed to the original document: Diego PettenòThey are listed here as the Wiki history does not allow for any external attribution.

yes checking for g++ option to produce PIC... -fPIC -DPIC checking if g++ PIC flag -fPIC -DPIC works... If you want to use that, > you should regenerate the build system entirely. > aclocal.m4:14: the top level > autom4te: /usr/bin/m4 failed with exit status: 63 > autoheader: '/usr/bin/autom4te' failed I can confirm this problem occurs on Ubuntu 8.10. comment:4 Changed 7 years ago by mloskot I can confirm the r1650 works.