Libtool Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn libtool version mismatch error. this is libtool 2.4.6 but the more about Stack Overflow the company Business Learn more about hiring developers or posting
Libtool Version-info
ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack
Definition Of This Lt_init Comes From An Older Release
Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up error: Libtool library used but 'LIBTOOL' is undefined up vote 37
Install Libtool Ubuntu
down vote favorite 5 I am trying to automake the OrientDb C++ library, but getting some errors. Makefile.am:10: error: Libtool library used but 'LIBTOOL' is undefined Makefile.am:10: The usual way to define 'LIBTOOL' is to add 'LT_INIT' Makefile.am:10: to 'configure.ac' and run 'aclocal' and 'autoconf' again. Makefile.am:10: If 'LT_INIT' is in 'configure.ac', make sure Makefile.am:10: its definition is in aclocal's search path. https://github.com/tglman/orientdb-c https://github.com/tglman/orientdb-c/wiki/Install I have configure.ac and lt_init aclocal search path Makefile.am already defined. I run the following autotools aclocal autoheader automake: libtool (GNU libtool) 2.4.2 configure.ac # -*- Autoconf -*- # Process this file with autoconf to produce a configure script. AC_PREREQ([2.69]) AC_INIT([orientdb-c],[0.9]) AC_CONFIG_SRCDIR([src/o_query_internal.h]) AC_CONFIG_HEADERS([config.h]) AM_INIT_AUTOMAKE() # Checks for programs. AC_PROG_CXX AC_PROG_AWK AC_PROG_CC AC_PROG_CPP AC_PROG_INSTALL AC_PROG_LN_S AC_PROG_MAKE_SET LT_INIT # Checks for libraries. # Checks for header files. AC_CHECK_HEADERS([malloc.h memory.h netdb.h netinet/in.h stdlib.h string.h sys/ioctl.h sys/socket.h sys/time.h unistd.h]) # Checks for typedefs, structures, and compiler characteristics. AC_TYPE_SIZE_T # Checks for library functions. AC_FUNC_MALLOC AC_FUNC_REALLOC AC_CHECK_FUNCS([gethostbyname memset socket strchr strcspn strdup strerror]) AC_CONFIG_FILES([Makefile]) AC_OUTPUT Things I already tried: autoreconf aclocal -I /usr/share/libtool aclocal -I . c linux autotools orientdb share|improve this question edited Sep 24 '13 at 10:15 asked Sep 24 '13 at 9:52 Imme22009 1,09231639 3 So this pretty much sums up every autogen.sh or initgen.sh ever. –Brett Hale Oct 1 '13 at 13:23 4 For anyone else stumbling on this error the fix for me was: sudo apt-get install libtool. –Casper Mar 12 at 14:37 add a comment| 2 Answers 2 active oldest votes up vote 40 down vote Fixed it. I needed to run libtoolize in the directory, then re-run: aclocal autoheader share|improve this answer answered Sep 24 '13 at 11:12
interpreter: No such file or directory How to install Counter-Strike 1.6 Server → How to fix libtool: Version mismatch error May 28, 2012 | Filed under: GNU/Linux Hello, A couple of days ago I encountered the following issue when installing cdpath: command not found memcache using pecl: This should have been a simple thing, it is usually works libtool: line 481: cdpath: command not found using a simple command: pecl install memcache Unfortunately this time it did not, it just returned the following messages: libtool: Version mismatch lt_init: command not found error. This is libtool 2.2.10, but the libtool: definition of this LT_INIT comes from an older release. libtool: You should recreate aclocal.m4 with macros from libtool 2.2.10 The answer is simple and you have instructions on http://stackoverflow.com/questions/18978252/error-libtool-library-used-but-libtool-is-undefined what you have to do in the error message, so this is what you have to do: 1. Download the package: pecl download memcache 2. Extract the package && navigate to the right directory: tar -zxvf memcache-2.2.6.tgz cd memcache-2.2.6/ 3. Run phpize: phpize --clean phpize 4. Remove the aclocal.m4 file: rm aclocal.m4 5. Run aclocal and autoconf: aclocal autoconf 6. Now configure, make and install the package: ./configure make make install Everything should http://www.howtodoityourself.org/how-to-fix-libtool-version-mismatch-error.html work, if you encounter any other issues just read the error messages and follow the instructions. I have encountered the same problem with apc and geoip extensions also, I followed the same steps and managed to install these without any other issues. Did you like this article? Share it with your friends! Tweet Written by Cristian Visit my Website ← How to fix /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory How to install Counter-Strike 1.6 Server → 5 Responses to "How to fix libtool: Version mismatch error" nikita says: February 8, 2013 at 12:42 tnx 🙂 Reply Cristian says: February 9, 2013 at 02:21 You are welcome. Reply Seppe says: August 14, 2014 at 13:07 Thanks. This post helped me find out a lot more about the autoconf system. If someone is interested, a more in-depth tutorial on this matter can be found . Reply polo says: February 8, 2015 at 06:46 Thanks, you saved me! Reply omid says: March 12, 2015 at 23:15 Thanks man It Really helped me . Reply Leave a Reply Cancel reply Your email address will not be published. Required fields are marked *Comment Name * Email * Website Links My Science Is Better Archives May 2015 September 2014 August 2014 June 2014 April 2014 March 2014 February 2
so that the generated libtool script will understand the characteristics of the host. It’s https://www.gnu.org/s/libtool/manual/html_node/LT_005fINIT.html the most important of a number of macros defined by Libtool: Macro: LT_PREREQ (version) Ensure that a recent enough version of Libtool is being used. If the version of Libtool used for LT_INIT is earlier than version, print an error message to the standard error output and exit with failure (exit status command not is 63). For example: LT_PREREQ([2.4.6]) Macro: LT_INIT (options) Macro: AC_PROG_LIBTOOL Macro: AM_PROG_LIBTOOL Add support for the --enable-shared, --disable-shared, --enable-static, --disable-static, --with-pic, and --without-pic configure flags.6 AC_PROG_LIBTOOL and AM_PROG_LIBTOOL are deprecated names for older versions of this macro; autoupdate will upgrade your configure.ac files. By default, this macro turns on shared libraries if they command not found are available, and also enables static libraries if they don’t conflict with the shared libraries. You can modify these defaults by passing either disable-shared or disable-static in the option list to LT_INIT, or using AC_DISABLE_SHARED or AC_DISABLE_STATIC. # Turn off shared libraries during beta-testing, since they # make the build process take too long. LT_INIT([disable-shared]) The user may specify modified forms of the configure flags --enable-shared and --enable-static to choose whether shared or static libraries are built based on the name of the package. For example, to have shared ‘bfd’ and ‘gdb’ libraries built, but not shared ‘libg++’, you can run all three configure scripts as follows: trick$ ./configure --enable-shared=bfd,gdb In general, specifying --enable-shared=pkgs is the same as configuring with --enable-shared every package named in the comma-separated pkgs list, and every other package with --disable-shared. The --enable-static=pkgs flag behaves similarly, but it uses --enable-static and --disable-static. The same applies to the --enable-fast-install=pkgs flag, which uses --enable-fast-insta