Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: torsten <torsten@inetw.net>
To: alsa-devel@lists.sourceforge.net
Subject: wolk kernel headers
Date: Mon, 10 Feb 2003 16:14:42 -0500	[thread overview]
Message-ID: <20030210161442.55d398cd.torsten@inetw.net> (raw)

Hello,

I've run into a problem.  I installed my machine with
a non-wolk kernel.  Now I'm running a wolk kernel.  I need
the integrated sound to keep my laptop from crashing on
suspend.

Since the kerenel headers copied into /usr/include match
the glibc when my kernel was compiled (non-wolk), there
are no files asound.h and asequencer.h (needed by kdelibs).

I cannot compile the alsa-driver package against the running
wolk kernel (it complains that I haven't enable sound).

There are header files in alsa-driver, and in the wolk kernel
tree.

Should I just copy the needed headers into /usr/include?

Torsten



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

             reply	other threads:[~2003-02-10 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 21:14 torsten [this message]
2003-02-11  8:36 ` wolk kernel headers Takashi Iwai
2003-02-11 21:34   ` torsten

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=20030210161442.55d398cd.torsten@inetw.net \
    --to=torsten@inetw.net \
    --cc=alsa-devel@lists.sourceforge.net \
    /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