Re: [Help-gnunet] trouble with cvs

[Benjamin Kay]

On Sunday 02 November 2003 08:36 pm, Christian Grothoff wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Sunday 02 November 2003 01:28 pm, Benjamin Kay wrote:
> > Libtool 1.5.0 and 1.5.0a are still cvs at the moment and, not
> > suprisingly, the libtool bootstrap script doesn't work either. Unless
> > anyone has any more ideas it looks like I'm stuck until the next release
> > of GNUnet :-(
> >
> > If it turns out that libtool 1.5.0a is indeed required to build GNUnet
> > from cvs, someone should update this page:
> > http://www.ovmj.org/GNUnet/download.php3?xlang=English
>
> It's more complicated than that, the magic seems to be in the combination.
> Here are the results of 3 tests that I just did:
>
> Works:
> gcc version    : 2.96
> Gnu gmake      : 3.79.1
> autoconf       : 2.13
> automake       : 1.7.2
> libtool        : 1.4.2
>
>
> Works:
> gcc version    : gcc (GCC) 3.3.2 (Debian)
> Gnu make       : 3.80
> autoconf       : 2.57
> automake       : 1.4-p6
> libtool        : 1.5.0a
>
>
> Fails:
> gcc version    : gcc (GCC) 3.3.1 20030626 (Debian prerelease)
> Gnu make       : 3.80
> autoconf       : 2.57
> automake       : 1.4-p4
> libtool        : 1.4.3
>
>
> So the answer is: it is not quite clear which combinations work.  In
> general, the theme is that the developers fix problems if something does
> not work with the latest version, so if you have the latest version of all
> build tools (as in: the latest release) and it breaks, we'll try our best
> to fix it.  Sadly, the autotools are so messy that I don't think there's
> any good way of supporting "all" combinations, especially since their
> styles contradict each other sometimes.
>
>
> Christian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
>
> iD8DBQE/pWrk9tNtMeXQLkIRAu/lAJ9qWVPzxrnvUWdEiO3UuvYElBrTygCfRE70
> Sm7p/n96146Hb5oS5wtkQ6s=
> =tHKR
> -----END PGP SIGNATURE-----

Did some guess-and-check of my own:

Fails:
gcc version     : 3.2.3
Gnu make                : 3.80
autoconf                : 2.13
automake                : 1.7.8
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.57a
automake                : 1.7.8
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.57a
automake                : 1.7.2
libtool         : 1.4.3

Fails, says autoconf 2.57 or higher is required:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.54
automake                : 1.7.2
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.13
automake                : 1.7.2
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.53a
automake                : 1.7.2
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.57a
automake                : 1.6.3
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.57a
automake                : 1.7.5
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.57a
automake                : 1.6.1
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.13
automake                : 1.6.1
libtool         : 1.4.3

Fails:
gcc version     : 3.3.2
Gnu make                : 3.80
autoconf                : 2.13
automake                : 1.7.5
libtool         : 1.4.3

and so on and so forth

On Sunday 02 November 2003 10:58 pm, Glenn McGrath wrote:
> bootstrap.sh runs autoreconf, most distributions have a wrapper around
> various autotools to aid in compatability, the wrapper will look for
> certain things to decide which version of the autotool to run.

> snip <

> If you have multiple versions of autotools installed and the wrapper
> isnt doing its job then try and run the commands manually, i.e.
>
> aclocal-1.7
> automake1-1.7 -a -f (-a means add files, -f force)
> autoconf-2.57 -i -f (-i means insert (add) files, -f force)

OK, tried doing it your way...
cd GNUnet
cd libltdl
aclocal-1.x
autoconf-2.57 -i -f
automake-1.x -a -f
(in x = 4, "automake-1.4 -a")

automake-1.x where x is greater than 4 always fails with:
configure.ac:54: required file `./config-h.in' not found

automake-1.4 fails spectacularly with:
automake: configure.ac: installing `[.]/install-sh'; error while making link: 
No such file or directory

automake: configure.ac: installing `[.]/mkinstalldirs'; error while making 
link: No such file or directory

automake: configure.ac: installing `[.]/missing'; error while making link: No 
such file or directory

configure.ac: 173: required file `[.]/ltmain.sh' not found
configure.ac: 173: installing `[.]/config.guess'; error while making link: No 
such file or directory

configure.ac: 173: installing `[.]/config.sub'; error while making link: No 
such file or directory

automake: configure.ac: installing `[.]/config.guess'; error while making 
link: No such file or directory

automake: configure.ac: installing `[.]/config.sub'; error while making link: 
No such file or directory

configure.ac: 54: required file `./config-h.in]' not found

And automake-2.57 when run after aclocal-1.5 does not fail, but warns:
configure.ac:54: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
configure.ac:79: warning: do not use m4_regexp: use regexp or m4_bregexp

Oh, and for the record, "autoconf-2.13" always fails with:
autoconf: configure.in: No such file or directory

Ideas?