From: Mikael Pettersson <mikpe@csd.uu.se>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can't build sound drivers as modules (2.5.55)
Date: Fri, 10 Jan 2003 07:55:37 +0100 [thread overview]
Message-ID: <15902.28265.876060.314756@harpo.it.uu.se> (raw)
In-Reply-To: <1042147153.4870.66.camel@dell_ss3.pdx.osdl.net>
Stephen Hemminger writes:
> When I try to install with sound as a configured module:
>
> WARNING: /lib/modules/2.5.55/kernel/sound/soundcore.ko needs unknown
> symbol
> errno
>
> This is new in 2.5.55, not sure where the missing bogus definition is.
> It looks like soundcore.ko contains sound_firmware.o which is seems to
> be more of an application than a driver (open/close)...
Someone removed the 'static int errno;' declaration in sound_firmware.c.
The sys calls it uses are apparently user-space versions with errno references.
The real fix is to delete the file altogether :-) Like the comments in it
say, firmware should be inserted by a user-space application.
prev parent reply other threads:[~2003-01-10 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 21:19 Can't build sound drivers as modules (2.5.55) Stephen Hemminger
2003-01-10 6:55 ` Mikael Pettersson [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=15902.28265.876060.314756@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=shemminger@osdl.org \
/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.