All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ivica Bukvic" <ico@fuse.net>
To: alsa-devel@alsa-project.org
Subject: Another question/note regarding CVS compile process
Date: Wed, 15 May 2002 18:43:57 -0400	[thread overview]
Message-ID: <000001c1fc61$fffe07b0$ac1f830a@ico> (raw)

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'

And then it seems to stop the ./build prep process since when I do the
same steps by hand and try to configure afterwards, I get the following
errors:

./configure: line 543: syntax error near unexpected token
'AM_CONDITIONAL(INSTALL_M4,'
./configure: line 543: 'AM_CONDITIONAL(INSTALL_M4, test "x$(ACLOCAL)" =
"xaclocal")'

This does not happen when I do a simple cvscompile in the alsa-driver
folder.

I do already have an entry in the /usr/share/aclocal/alsa.m4 which I do
not know whether it has anything to do with this but it seems when I
rename it it makes no difference.

But, what I just discovered this very moment is that when I remove the
alsa.m4 (or its renamed incarnation) from the /usr/share/aclocal, I do
not get these errors. Maybe this should be done automatically since
otherwise build script fails.

Ico




_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net

             reply	other threads:[~2002-05-15 22:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 22:43 Ivica Bukvic [this message]
2002-05-16  1:30 ` Another question/note regarding CVS compile process Andy Wingo
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='000001c1fc61$fffe07b0$ac1f830a@ico' \
    --to=ico@fuse.net \
    --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 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.