All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michel Dänzer <michdaen@iiic.ethz.ch>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: problems when recompiling dmasound modules
Date: Fri, 05 Jan 2001 16:10:58 +0100	[thread overview]
Message-ID: <3A55E402.DA790B96@iiic.ethz.ch> (raw)
In-Reply-To: 200101041317.NAA24882@hyperion.valhalla.net


Iain Sandoe wrote:

> > so they rely on `make oldconfig' and `make dep' instead...
>
> vi Makefile, change EXTRAVERSION to append -ids (my usual kinda practice)...
>
> make oldconfig dep vmlinux modules
>
>  - builds dmasound_core & dmasound_awacs
>
> make_install creates a new /lib/modules/2.4.0-test13-pre3-ids and the
> modules appear to be installed...
>
> so... it seems to work for me.

The problem only shows up when I boot the new kernel and try to insmod the
dmasound modules, have you tried that?


If make dep is always needed after make oldconfig that may be the problem as I
also rely on make oldconfig telling me if I have to do that. (real men, you
know ;)


I'll report back when I've had the chance to test that.

Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and The DRI Project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-01-05 15:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 13:17 problems when recompiling dmasound modules Iain Sandoe
2001-01-05 15:10 ` Michel Dänzer [this message]
2001-01-05 15:20   ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2001-01-05 15:58 Iain Sandoe
2001-01-05 21:20 ` Michel Dänzer
2001-01-04  9:56 Iain Sandoe
2001-01-04 11:51 ` Geert Uytterhoeven
2001-01-04  3:59 Michel Dänzer

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=3A55E402.DA790B96@iiic.ethz.ch \
    --to=michdaen@iiic.ethz.ch \
    --cc=geert@linux-m68k.org \
    --cc=iain@sandoe.co.uk \
    --cc=linuxppc-dev@lists.linuxppc.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.