From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Pfeiffer <roto@gmx.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty
Date: Thu, 11 May 2006 09:49:03 +1000 [thread overview]
Message-ID: <1147304943.32448.86.camel@localhost.localdomain> (raw)
In-Reply-To: <20060510230811.GH3878@localhost>
On Thu, 2006-05-11 at 01:08 +0200, Wolfgang Pfeiffer wrote:
> On Wed, May 10, 2006 at 11:30:28PM +0200, Wolfgang Pfeiffer wrote:
> > On Wed, May 10, 2006 at 06:04:13PM +0200, Johannes Berg wrote:
> >
> > > Also, try snd-aoa.
> >
> > Impossible here, it does not compile here. Neither with gcc 4.0 or 4.1
> >
>
> Not being sure tho' whether the fact my source dir for the running
> kernel is cleaned up, IINM, (like "fakeroot make-kpkg clean") is the
> culprit for the failed compile ... I'll have a look into that at
> next daylight ... :)
You can't build modules with "cleaned" kernel headers.
Ben.
next prev parent reply other threads:[~2006-05-10 23:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 15:49 Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty Wolfgang Pfeiffer
2006-05-10 16:04 ` Johannes Berg
2006-05-10 17:24 ` Wolfgang Pfeiffer
2006-05-10 20:54 ` Christoph Cebulla
2006-05-10 23:48 ` Benjamin Herrenschmidt
2006-05-10 21:30 ` Wolfgang Pfeiffer
2006-05-10 23:08 ` Wolfgang Pfeiffer
2006-05-10 23:49 ` Benjamin Herrenschmidt [this message]
2006-05-12 14:19 ` Wolfgang Pfeiffer
2006-05-12 14:27 ` Johannes Berg
2006-05-10 23:47 ` Benjamin Herrenschmidt
2006-05-11 11:58 ` Johannes Berg
2006-05-11 12:04 ` Benjamin Herrenschmidt
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=1147304943.32448.86.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=johannes@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=roto@gmx.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 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.