search

theRockLiu / googletest

Automatically exported from code.google.com/p/googletest
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

configure.ac:29: error: possibly undefined macro: AC_PROG_LIBTOOL #236

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. svn checkout http://googletest.googlecode.com/svn/trunk/
googletest-read-only
2. cd googletest-read-only
3. autoreconf -fvi

What is the expected output? What do you see instead?

googletest-read-only> autoreconf -fvi
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.ac:29: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1

What version of the product are you using? On what operating system?

64-bit openSUSE 11.1

> uname -srvmpio
Linux 2.6.27.37-0.1-default #1 SMP 2009-10-15 14:56:58 +0200 x86_64 x86_64
x86_64 GNU/Linux

> /usr/local/bin/aclocal --version
aclocal (GNU automake) 1.11
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <tromey@redhat.com>
       and Alexandre Duret-Lutz <adl@gnu.org>.

> /usr/local/bin/automake --version
automake (GNU automake) 1.11
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Tom Tromey <tromey@redhat.com>
       and Alexandre Duret-Lutz <adl@gnu.org>.

Original issue reported on code.google.com by jeff.science@gmail.com on 20 Dec 2009 at 5:55

GoogleCodeExporter commented 9 years ago 
We'll probably switch the build system from autotools to something else, so the
priority is low.

Chandler, anything obvious?  Thanks.

Original comment by w...@google.com on 21 Dec 2009 at 7:01

GoogleCodeExporter commented 9 years ago 
I find autotools to be a royal pain.  It would be great if they died a quick and
painful death.

While I reported the error on my laptop, I want to use Google's test and perf 
tools
on BlueGene/P, which is a hideous cross-compile unless one spends a few days
debugging autoconf.  Hence, just about any other build system would be very 
useful.

Thanks,

Jeff

Original comment by jeff.science@gmail.com on 21 Dec 2009 at 7:07

GoogleCodeExporter commented 9 years ago 
The makefile/ folder contains a Makefile.  You can use that instead of 
autotools.

I've made some progress on the CMake scripts.  I'll try to commit them to the 
SVN
soon s.t. people can play with them.

Original comment by w...@google.com on 23 Dec 2009 at 2:53

GoogleCodeExporter commented 9 years ago 
We are switching away from autotools.

Original comment by w...@google.com on 23 Dec 2009 at 7:08