From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mikael Magnusson <mikaelmagnusson@glocalnet.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: alsa-tools: cvscompile fails at ./configure for qlo10k1
Date: Tue, 29 Mar 2005 15:13:51 -0500 [thread overview]
Message-ID: <1112127231.5141.4.camel@mindpipe> (raw)
In-Reply-To: <s5hsm2eiqv2.wl@alsa2.suse.de>
On Tue, 2005-03-29 at 14:22 +0200, Takashi Iwai wrote:
> At Sun, 27 Mar 2005 23:46:50 +0200,
> Mikael Magnusson wrote:
> >
> > On Fri, Mar 25, 2005 at 09:53:57PM -0500, Lee Revell wrote:
> > ...
> > > aclocal:configure.in:12: warning: macro `AM_PATH_LD10K1' not found in library
> > > configure.in:12: error: possibly undefined macro: AM_PATH_LD10K1
> > > If this token and others are legitimate, please use m4_pattern_allow.
> > > See the Autoconf documentation.
> > > autoreconf: /usr/bin/autoconf failed with exit status: 1
> > ...
> > >
> >
> > AM_PATH_LD10K1 is defined in ld10k1.m4, which should have been installed
> > when you installed ld10k1.
>
> Yes. Also, ld10k1 requires as10k1 in advance (to compile examples).
> This should be mentioned in README...
OK. People who expect ./cvscompile to just work will consider this a
bug though. I guess if there is a bug it's that the cvscompile script
does not handle pre-dependencies.
Lee
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-29 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 2:53 alsa-tools: cvscompile fails at ./configure for qlo10k1 Lee Revell
2005-03-27 21:46 ` Mikael Magnusson
2005-03-29 12:22 ` Takashi Iwai
2005-03-29 20:13 ` Lee Revell [this message]
2005-03-30 10:13 ` 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=1112127231.5141.4.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mikaelmagnusson@glocalnet.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.