Re: [Help-gnunet] current cvs not compiling

[Christian Grothoff]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Whenever we change configure.in, you must re-run autogen.sh for the CVS 
versions. CVS does compile and no, it's ok if people try it out, 0.4.9 nodes 
will just not be able to connect to 0.4.6 nodes, but there would not be a 
problem with running both versions in parallel on the Internet.

Christian

On Monday 16 September 2002 11:32 am, address@hidden wrote:
> At the moment the current cvs code isn't (or for that matter hasn't
> been) compiling because of a couple macros set up in configure.in
> referring to automake. Basically the lines are being copied straight
> from configure.in to configure, which prevents compilation. The error in
> configure is:
>
> ./configure: line 536: syntax error near unexpected token `GNUnet,'
> ./configure: line 536: `AM_INIT_AUTOMAKE(GNUnet, 0.4.9)'
>
> I think this is because there is no src/include/autodefs.h
>
> I started reading up on the autoconf documentation figuring that either
> automake is botched on my system, there is a simple mistake in
> configure.in, or that autodefs is some trivial file was accidentally
> forgotten.
>
> Then I started thinking about it and realized that it was possible
> that configure.in was intentionally botched (or autodefs.h intentionally
> not included) in order to discourage 0.4.9 nodes from showing up on the
> network.
>
>
> Should I get to work finally learning the ins and outs of autoconf, or
> should I be a good little user and keep my hands to myself?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9hgwN9tNtMeXQLkIRAkXhAJwIDh1g4nsHuRygihNWdf5wQLEcfQCgkLql
r39XGraD8MZ6ZCqU4LGCSB4=
=vHj0
-----END PGP SIGNATURE-----