All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: macro `AM_PATH_ALSA' not found in library
Date: Wed, 05 Jul 2006 18:20:26 -0400	[thread overview]
Message-ID: <1152138027.15837.174.camel@mindpipe> (raw)
In-Reply-To: <1152127459.15837.127.camel@mindpipe>

On Wed, 2006-07-05 at 15:24 -0400, Lee Revell wrote:
> I have a script that builds alsa-lib and alsa-utils for an embedded
> platform.
> 
> It works perfectly on all my Ubuntu machines.  But when I try it on an
> FC4 box, alsa-lib builds correctly, but alsa-utils fails like so:
> 

OK, I've tried to resolve this by having my script run "cvscompile".
But it stops at:

"Copying file m4/xsize.m4

Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
You need aclocal from GNU automake 1.5 (or newer) to do this.
Then run 'autoconf' to regenerate the configure file.

You might also want to copy the convenience header file gettext.h
from the /usr/share/gettext directory into your package.
It is a wrapper around <libintl.h> that implements the configure
--disable-nls
option.

Press Return to acknowledge the previous two paragraphs."

I cannot press return here because I must be able to build
non-interactively using a script.

How can I silence these warnings?  Even if I run "aclocal -I m4" then
"autoconf" I still get this prompt on the next build.

Lee




Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-07-05 22:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 19:24 macro `AM_PATH_ALSA' not found in library Lee Revell
2006-07-05 22:20 ` Lee Revell [this message]
2006-07-06 10:28   ` Takashi Iwai
2006-07-06 10:27 ` 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=1152138027.15837.174.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.