Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configure of distcc-3.0 faails #23

Closed
GoogleCodeExporter opened this issue Mar 31, 2016 · 4 comments
Closed

configure of distcc-3.0 faails #23

GoogleCodeExporter opened this issue Mar 31, 2016 · 4 comments

Comments

@GoogleCodeExporter
Copy link

When I retrieve the latest source (http://distcc.googlecode.com/files/
distcc-3.0.tar.bz2) and try to build it, I get the following error when 
running configure:
./configure: line 8145: syntax error near unexpected token `AVAHI,'
./configure: line 8145: `    PKG_CHECK_MODULES(AVAHI, avahi-client >= 0.6,'

Running autogen.sh before produces the following output:
./autogen.sh: running aclocal
aclocal: couldn't open directory `m4': No such file or directory
./autogen.sh: running autoheader
./autogen.sh: running autoconf
configure.ac:90: error: possibly undefined macro: AC_DEFINE
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.

This happens on 2 different machines (both Linux, same errors):
CentOS something
autoconf (GNU Autoconf) 2.59
automake (GNU automake) 1.9.6

Debian testing
autoconf (GNU Autoconf) 2.61
automake (GNU automake) 1.10.1

Original issue reported on code.google.com by metalh...@metalhead.ws on 13 Oct 2008 at 10:46

@GoogleCodeExporter
Copy link
Author

To build from the distcc 3.0 source distribution, just unpack it and run 
"./configure" and then "make" - do 
NOT run autoconf or autogen.sh.  If you just run configure and make, without 
running autoconf or 
autogen.sh, then you won't get the errors that you reported.

That said, it ought to work even if you run autoconf or autogen.sh.  I was able 
to reproduce the errors that 
you reported, by running autoconf before running configure.  The reason that 
this fails is that we don't 
include the "m4" directory in the source distribution - that's a bug, IMHO.
The following patch should fix it (for future source distributions).

Index: Makefile.in
===================================================================
--- Makefile.in (revision 617)
+++ Makefile.in (working copy)
@@ -114,7 +114,7 @@
        $(dist_extra)                                           \
        $(gnome_data)

-dist_dirs = include_server/test_data
+dist_dirs = m4 include_server/test_data

 dist_lzo = lzo/minilzo.c lzo/minilzo.h lzo/lzoconf.h lzo/.stamp-conf.in


Original comment by fergus.h...@gmail.com on 26 Oct 2008 at 6:58

@GoogleCodeExporter
Copy link
Author

Original comment by fergus.h...@gmail.com on 26 Oct 2008 at 6:59

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

I've submitted that patch to the repository.
So now this will be fixed as soon as we do the next release.

Original comment by fergus.h...@gmail.com on 27 Oct 2008 at 2:19

@GoogleCodeExporter
Copy link
Author

Fixed in distcc 3.1.

Original comment by fergus.h...@gmail.com on 3 Dec 2008 at 12:04

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant