Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: alsa-devel@alsa-project.org
Subject: Re: Another question/note regarding CVS compile process
Date: Wed, 15 May 2002 21:30:26 -0400	[thread overview]
Message-ID: <20020516013025.GF608@jesus> (raw)
In-Reply-To: <000001c1fc61$fffe07b0$ac1f830a@ico>

On Wed, 15 May 2002, Ivica Bukvic wrote:

> One more thing I noticed about my build process:
> 
> When I do ./build prep
> 
> I get the following response:
> 
> aclocal: ../alsa-lib/utils/alsa.m4: 15: duplicated macro 'AM_PATH_ALSA'

This is buggy behavior on the part of aclocal. aclocal comes with
automake, if I recall correctly; upgrade your automake and this error
will go away. Mine is 1.5, as I have automake 1.5. The 1.4 series might
still have this bug, I don't know.

regards,

wingo.

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  reply	other threads:[~2002-05-16  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 22:43 Another question/note regarding CVS compile process Ivica Bukvic
2002-05-16  1:30 ` Andy Wingo [this message]
2002-05-16  9:23 ` 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=20020516013025.GF608@jesus \
    --to=wingo@pobox.com \
    --cc=alsa-devel@alsa-project.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox