From: Andrei Boros <andrei@srr.ro>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: cvs alsa-lib compilation :
Date: Wed, 24 Sep 2003 14:29:25 +0300 [thread overview]
Message-ID: <3F718015.6954A110@srr.ro> (raw)
In-Reply-To: s5hbrtbr2i0.wl@alsa2.suse.de
Takashi Iwai wrote:
> > gate:~/install/alsa-cvs/alsa-lib# ./cvscompile
> > configure.in:44: warning: do not use m4_patsubst: use patsubst or
> > m4_bpatsubst
> > configure.in:182: warning: do not use m4_regexp: use regexp or
> > m4_bregexp
> > autoheader: `include/config.h.in' is unchanged
> > CFLAGS=-O2 -Wall -W -pipe -g
>
> ARGH, again autotools problem!
>
> please tell me the version of automake, autoconf and libtool.
> and check which tool causes this error by running the sequence in
> cvscompile script manually.
>
gate:~/install/alsa-cvs/alsa-utils/alsactl# automake --version
automake (GNU automake) 1.5
gate:~/install/alsa-cvs/alsa-utils/alsactl# autoconf --version
autoconf (GNU Autoconf) 2.53
gate:~/install/alsa-cvs/alsa-utils/alsactl# libtool --version
ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52)
Running each command in cvscompile :
gate:~/install/alsa-cvs/alsa-lib# autoheader
configure.in:44: warning: do not use m4_patsubst: use patsubst or
m4_bpatsubst
configure.in:182: warning: do not use m4_regexp: use regexp or
m4_bregexp
autoheader: `include/config.h.in' is unchanged
--
ing. Andrei Boros
mailto:andrei@srr.ro / +40-21-303-1870
Centrul pt. Tehnologia Informatiei
Societatea Romana de Radiodifuziune
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-09-24 11:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 9:06 cvs alsa-lib compilation : Andrei Boros
2003-09-23 14:41 ` Takashi Iwai
2003-09-24 11:29 ` Andrei Boros [this message]
2003-09-24 14:09 ` Takashi Iwai
2003-09-25 2:54 ` Andrei Boros
2003-09-25 3:46 ` Andrei Boros
2003-09-25 9:16 ` Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F718015.6954A110@srr.ro \
--to=andrei@srr.ro \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.