[leafnode-list] Re: Current version of leafnode 2? Missing configure file?

[Matthias Andree]

Am 25.06.2015 um 15:57 schrieb Adam Funk:
> On 2015-06-25, Adam Funk wrote:
> 
>> I'm trying to install leafnode 2 on a new machine.  Is this the right
>> place to get the current version from?
>>
>> <https://gitlab.com/leafnode-2/leafnode-2/>
>>
>> If so, how do I run the './configure --.....' step?  There's no
>> configure file.
> 
> OK, I guess I need to use autoconf for this ... what do I do with the
> error messages?
> 
> $ autoconf configure.ac >configure

You don't normally redirect the output for autoconf - it writes
"configure" by itself.

>  configure.ac:7: error: possibly undefined macro: AM_INIT_AUTOMAKE
>        If this token and others are legitimate, please use m4_pattern_allow.
>        See the Autoconf documentation.
> configure.ac:8: error: possibly undefined macro: AM_SILENT_RULES
> configure.ac:22: error: possibly undefined macro: AM_PROG_CC_C_O
> configure.ac:122: error: possibly undefined macro: AM_WITH_DMALLOC
> $ chmod u+x configure
> $ ./configure
> ./configure: line 2120: syntax error near unexpected token `silent-rules'
> ./configure: line 2120: `AM_INIT_AUTOMAKE(silent-rules)'
> 

Hi Adam,

autoconf is only part of the rigging, you also need automake and
aclocal, and in proper order. More below.

Interlude: The easy way for you is to grab ready-made tarballs -
unfortunately, some guys at uni-dortmund.de decided it's time to pull
the plug on the old domain name and rename to tu-dortmund.de, and the
current admin apparently has not invoked the exception clause;
unfortunately I figured that home.pages.de, the forwarder, also pulled
the plug on its configuration interface - I can't seem to find a way to
change the destination, so I need to consider that defunct, too.


Back to the original topic, tarballs are available from

http://www.dt.e-technik.tu-dortmund.de/~ma/leafnode/beta/

for now.  Or else if someone wants to build from a Git clone, run

	autoreconf --install --symlink --verbose

which sorts out the proper calling order of automake, autoconf, aclocal
(which I think was the missing part) and thereabouts, and calls them for
you, such that you get a working ./configure script.

HTH
Matthias