From: Takashi Iwai <tiwai@suse.de>
To: Andrei Boros <andrei@srr.ro>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: dummy sequencer module problems
Date: Thu, 20 Mar 2003 11:32:11 +0100 [thread overview]
Message-ID: <s5hadfqs504.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E797BC9.F4EB1348@srr.ro>
At Thu, 20 Mar 2003 10:28:57 +0200,
Andrei Boros wrote:
>
> <<<<<<< Makefile.conf.in
> CONFIG_SND_SEQ_DUMMY = @CONFIG_SND_SEQ_DUMMY@
> =======
> CONFIG_SND_SEQ_DUMMY = @CONFIG_SND_SEQUENCER@
> >>>>>>> 1.52
>
> I got again this inconsistency in Makefile.conf.in when updateing the
> cvs tree.
>
> I am wandering, this looks to me that snd-seq-dummy.o will be built
> always if sequencer is built, regardless of the fact that the dummy
> soundcard driver is built or not. I checked the Makefile in
> alsa-kernel/core/seq.
yes, we don't provide the configure option for this yet, so i just
wrote like the above. (i.e. seq-dummy is provided always if sequencer
is enabled).
note that snd-seq-dummy is completely different thing from snd-dummy.
please don't make them together.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Tablet PC.
Does your code think in ink? You could win a Tablet PC.
Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
prev parent reply other threads:[~2003-03-20 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 10:45 sequencer module problems Andrei Boros
2003-03-19 11:29 ` Takashi Iwai
[not found] ` <3E7863A8.B5BACE35@srr.ro>
2003-03-19 13:41 ` Takashi Iwai
2003-03-20 8:17 ` Typo in configure.in : dummy sequencer Andrei Boros
2003-03-20 8:28 ` Jaroslav Kysela
2003-03-20 8:20 ` alsa-driver, make 3.79, cvscompile Andrei Boros
2003-03-20 10:33 ` Takashi Iwai
[not found] ` <3E799CB6.EB6ED828@srr.ro>
2003-03-20 10:58 ` Takashi Iwai
2003-03-20 8:28 ` dummy sequencer module problems Andrei Boros
2003-03-20 10:32 ` 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=s5hadfqs504.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andrei@srr.ro \
/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.