From: Takashi Iwai <tiwai@suse.de>
To: peter plessas <plessas@mur.at>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: cvs compile, toplevel.config.in and alsa-kernel SOLVED
Date: Mon, 21 Mar 2005 21:27:16 +0100 [thread overview]
Message-ID: <s5hzmww3ftn.wl@alsa2.suse.de> (raw)
In-Reply-To: <423DB1EC.3000300@mur.at>
At Sun, 20 Mar 2005 18:25:00 +0100,
peter plessas wrote:
>
> Replying to my own mail:
>
> I took the cvs snapshots from http://alsa-project.org/alsa/ftp/
> which include a toplevel.config.in file.
>
> Problem solved!
Hmm, basically toplevel.config.in, ainclude.m4 and
include/config1.h.in are generated from utils/mod-deps program.
They should be created automatically via Makefile...
Takashi
-------------------------------------------------------
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
prev parent reply other threads:[~2005-03-21 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 17:25 cvs compile, toplevel.config.in and alsa-kernel SOLVED peter plessas
2005-03-21 20:27 ` Takashi Iwai [this message]
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=s5hzmww3ftn.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=plessas@mur.at \
/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