[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Protux-devel] Change of autoconf strategy in CVS
From: |
Reinhard |
Subject: |
Re: [Protux-devel] Change of autoconf strategy in CVS |
Date: |
Wed, 18 Feb 2004 20:43:40 +0100 |
User-agent: |
KMail/1.5 |
Am Dienstag, 17. Februar 2004 23:36 schrieb Martin Herren:
> Hej,
>
> ok, i commited the changes for Mustux to CVS.
> The first time you'll update Mustux, it will remove all unnecessary
> autotool files, so you'll have to rerun all autotools to regenerate them.
> After that everything should work, without the strange problems when
> running ./configure. If nobody experiences problems, i'll commit the same
> changes for Protux to CVS.
>
> Remainder about how to run autotools:
> $ aclocal
> $ autoheader
> $ libtoolize
> $ autoconf
> $ automake
> and a
> $ autoreconf --force
> can't be bad either.
>
> /Martin
Hi,
I did it, but got errors ...
address@hidden mustuxlib]$ aclocal
address@hidden mustuxlib]$ autoheader
address@hidden mustuxlib]$ libtoolize --force
Using `AC_PROG_RANLIB' is rendered obsolete by `AC_PROG_LIBTOOL'
address@hidden mustuxlib]$ autoconf
address@hidden mustuxlib]$ automake
configure.ac: required file `./install-sh' not found
configure.ac: required file `./mkinstalldirs' not found
configure.ac: required file `./missing' not found
Makefile.am: required file `./depcomp' not found
address@hidden mustuxlib]$
My machine:
MDK 9.1
address@hidden mustuxlib]$ autoconf --version
autoconf (GNU Autoconf) 2.57
address@hidden mustuxlib]$ automake --version
automake (GNU automake) 1.7.2
do you need more infos?
greetings
Reinhard