From: Andrew Veliath <andrewtv@usa.net>
To: "Jesper Juhl" <jesper.juhl@gmail.com>
Cc: "Adrian Bunk" <bunk@stusta.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: OSS msnd build failure
Date: 25 Feb 2006 10:38:48 -0800 [thread overview]
Message-ID: <m38xrz1dxj.fsf@zaphod.andrewtv.org> (raw)
In-Reply-To: <9a8748490602250841q32213603l50dd4142a9a107ae@mail.gmail.com>
Hi -- yes, it is looking to compile the firmware into the kernel so
that during boot it can access it in-memory. Despite showing it's age
as a driver, unfortunately we still probably cannot just include the
firmware for obvious reasons. I actually have an update for this
driver that I need to get around to patching up, so this kind of
reminded me.
thanks
Andrew
.........----------------==================----
..--==- Sat, 25 Feb 2006 17:41:54 +0100,
..--==- Jesper Juhl (JJ) discussed:
JJ) On 2/25/06, Adrian Bunk <bunk@stusta.de> wrote:
)) On Sat, Feb 25, 2006 at 05:24:10PM +0100, Jesper Juhl wrote:
))
)) > During some build tests of 2.6.16-rc4-mm2 with 'make randconfig' I
)) > found this build failure :
)) >
)) > ...
)) > LD drivers/built-in.o
)) > CC sound/sound_core.o
)) > CC sound/sound_firmware.o
)) > CC sound/oss/msnd.o
)) > make[2]: *** No rule to make target `/etc/sound/msndperm.bin', needed
)) > by `sound/oss/msndperm.c'. Stop.
)) > make[2]: *** Waiting for unfinished jobs....
)) > make[1]: *** [sound/oss] Error 2
)) > make: *** [sound] Error 2
)) >
)) > I must admit I don't know how to fix it, so I'll have to just report it.
))
)) That's expected if the .config contains CONFIG_STANDALONE=n
))
JJ) Ahhh, makes perfect sense, I should have thought of that.
JJ) Thanks Adrian.
JJ) --
JJ) Jesper Juhl <jesper.juhl@gmail.com>
JJ) Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
JJ) Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2006-02-25 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 16:24 OSS msnd build failure Jesper Juhl
2006-02-25 16:32 ` Adrian Bunk
2006-02-25 16:41 ` Jesper Juhl
2006-02-25 18:38 ` Andrew Veliath [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=m38xrz1dxj.fsf@zaphod.andrewtv.org \
--to=andrewtv@usa.net \
--cc=bunk@stusta.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).