From: Marcus Andersson <054185595@telia.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Knecht <mknecht@controlnet.com>, alsa-devel@lists.sourceforge.net
Subject: Re: hdsp and midi problems
Date: Mon, 23 Jun 2003 18:46:35 +0200 [thread overview]
Message-ID: <3EF72EEB.916B60D9@telia.com> (raw)
In-Reply-To: s5h1xxk3ga4.wl@alsa2.suse.de
Takashi Iwai wrote:
>
> hmm, i have no problem at all for compiling. what problem do you
> have?
True, I don't know what the current CVS status is.
> except for known compiler-check problem in the configure script, i've
> not heard much about it. at least, not reported to alsa-devel ML.
> (a few days ago, there was a missing file, but it was already fixed.)
Then this probably hit me the last time I tried to update. The problem
with alsa cvs is that, according to my experience, more often than not
it will not compile. This makes me think twice before I update my tree.
Developers should make an effort and check their code an extra time,
because a mistake affects so many.
Marcus
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
next prev parent reply other threads:[~2003-06-23 16:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 20:08 hdsp and midi problems Marcus Andersson
2003-06-21 20:14 ` Marcus Andersson
2003-06-23 13:38 ` Mark Knecht
2003-06-23 15:53 ` Marcus Andersson
2003-06-23 16:33 ` Takashi Iwai
2003-06-23 16:46 ` Marcus Andersson [this message]
2003-06-23 17:03 ` Takashi Iwai
2003-06-23 17:14 ` Marcus Andersson
2003-06-23 16:46 ` Jaroslav Kysela
2003-06-23 16:54 ` Takashi Iwai
2003-06-23 16:32 ` Takashi Iwai
2003-06-23 16:58 ` Mark Knecht
2003-06-23 17:11 ` Marcus Andersson
2003-06-23 18:12 ` Marcus Andersson
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=3EF72EEB.916B60D9@telia.com \
--to=054185595@telia.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mknecht@controlnet.com \
--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.