public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Norbert Breun <nbreun@gmx.de>
To: Peter Samuelson <peter@cadcamlab.org>,
	Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0-test13-pre3: Makefile problem in drivers/video
Date: Mon, 18 Dec 2000 08:02:23 +0100	[thread overview]
Message-ID: <00121808022301.00937@nmb> (raw)
In-Reply-To: <E147oeY-0006H7-00@mdj.nada.kth.se> <20001218001135.Z3199@cadcamlab.org>
In-Reply-To: <20001218001135.Z3199@cadcamlab.org>

Peter,

you may be right there is no module "video.o". The problem is, there should 
be a directory "media" under /lib/modules/2.4.0-test12.old/kernel/drivers/ 
and this is missing in test13pre2 and test13pre3. The modules are not built.

kind regards
Norbert


On Monday 18 December 2000 07:11, Peter Samuelson wrote:
> [Mikael Djurfeldt]
>
> > When trying to build video.o as a module, video.o doesn't get copied
> > to /lib/modules/* during installation.
>
> There is no video.o module.  If video.o is built at all, it is linked
> into the vmlinux image directly.  The modules in that directory will be
> atyfb.o, tdfxfb.o and about 800 others.
>
> Peter
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-18  7:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-18  0:59 2.4.0-test13-pre3: Makefile problem in drivers/video Mikael Djurfeldt
2000-12-18  6:11 ` Peter Samuelson
2000-12-18  7:02   ` Norbert Breun [this message]
2000-12-18  7:35     ` [PATCH] " Peter Samuelson
2000-12-18 14:49       ` Norbert Breun
2000-12-18 12:01     ` Alan Cox

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=00121808022301.00937@nmb \
    --to=nbreun@gmx.de \
    --cc=djurfeldt@nada.kth.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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