protux-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Protux-devel] migration from old autostuff to new


From: Martin Herren
Subject: Re: [Protux-devel] migration from old autostuff to new
Date: Tue, 11 Feb 2003 18:41:07 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1

Luciano Giordana wrote:

After fresh-reinstallation of newest autoconf automake (2.56 and 1.6) , here are the new outputs

libmustux compiles/install fines with simple configure / make / make install

at least one good news...

now protux :


address@hidden head]$ aclocal -I /usr/local/share/aclocal
aclocal: configure.ac: 26: macro `AM_PATH_ALSA' not found in library

did you try ./configure before trying aclocal ?
AM_PATH_ALSA is defined in the alsa.m4 file which comes with alsalib...
it is also defined in aclocal.m4, but if you want to run aclocal yoursel, you'll need to have alsa.m4 installed on your computer, so that aclocal can put AM_PATH_ALSA into your aclocal.m4. If you have alsa.m4 installed, you may need to specify the directory with the -I option to aclocal:
$ aclocal -i /path/to/your/alsa.m4_file/

address@hidden head]$ autoheader -I /usr/local/share/aclocal

(seems to work fine (no output))


address@hidden head]$ libtoolize --force
You should update your `aclocal.m4' by running aclocal.

(strange, I have just runned it :-(


address@hidden head]$ autoconf

(seems to work fine (no output))

address@hidden head]$ automake
configure.ac:5: no proper implementation of AM_INIT_AUTOMAKE was found,
configure.ac:5: probably because aclocal.m4 is missing...
configure.ac:5: You should run aclocal to create this file, then
configure.ac:5: run automake again.
/usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/lang-compile.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/depend2.am: AMDEP does not appear in AM_CONDITIONAL /usr/local/share/automake-1.6/am/lang-compile.am: AMDEP does not appear in AM_CONDITIONAL


address@hidden head]$ ./configure
checking for a BSD-compatible install... /usr//bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... missing
checking for working autoconf... found
checking for working automake-1.4... missing
checking for working autoheader... found
checking for working makeinfo... found
checking for g++... g++
checking for C++ compiler default output... a.out
checking whether the C++ compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a BSD-compatible install... /usr//bin/install -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for ld used by GCC... /usr//bin/ld
checking if the linker (/usr//bin/ld) is GNU ld... yes
checking for /usr//bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr//bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependant libraries... pass_all
checking command to parse /usr//bin/nm -B output... ok
checking how to run the C preprocessor... gcc -E
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... no
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr//bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking for abs in -lm... yes
checking for pthread_create in -lpthread... yes
checking for ALSA CFLAGS...
checking for ALSA LDFLAGS...  -lasound -lm -ldl -lpthread
checking for libasound headers version >= 0.9.0... found.

here it manages to call AM_PATH_ALSA... is that the output of your configure, or the one on cvs ?

checking for snd_ctl_open in -lasound... yes
./configure: line 8214: syntax error near unexpected token `0.17.0,,{'
./configure: line 8214: `AC_PATH_MUSTUX(0.17.0,,{ { echo "$as_me:$LINENO: error: *** Mustux is not installed or version is too old" >&5'
address@hidden head]$

strange...
if it is the output of your rebuilt configure, what is the error of the original one ? because if some of the autotool steps failed, chances are high that the output configure script is corrupt...

it seems as it couldn't find AC_PATH_MUSTUX to insert it into configure, so the function call remains... AC_PATH_MUSTUX is defined in mustux.m4, and gets installed under $prefix/share/aclocal/, so you need to add this path to aclocal with the -I option

/Martin






reply via email to

[Prev in Thread] Current Thread [Next in Thread]