From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: building a specific in-tree module is currently a bit broken
Date: Wed, 5 Sep 2007 05:16:12 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709050509150.27539@localhost.localdomain> (raw)
i know sam ravnborg has been Cc'ed on a janitors list posting
mentioning this but, just in case this note can get a fix snuck in
there quickly before 2.6.23 (this is on i386, but i'm guessing applies
to all arches):
$ make distclean
$ make defconfig
$ make menuconfig (select visor.ko to be built a module)
$ make drivers/usb/serial/visor.ko
scripts/kconfig/conf -s arch/i386/Kconfig
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-i386
CC arch/i386/kernel/asm-offsets.s
GEN include/asm-i386/asm-offsets.h
CALL scripts/checksyscalls.sh
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
HOSTCC scripts/bin2c
CC [M] drivers/usb/serial/visor.o
/bin/sh: .tmp_versions/visor.mod: No such file or directory
MODPOST 0 modules
$
whoops. manually creating the directory .tmp_versions first fixes
this, but i'm not conversant enough with the Makefile to want to take
a shot at repairing this.
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA
http://crashcourse.ca
========================================================================
next reply other threads:[~2007-09-05 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 9:16 Robert P. J. Day [this message]
2007-09-05 9:37 ` Michal Piotrowski
2007-09-05 9:43 ` Jan Engelhardt
2007-09-05 9:42 ` Robert P. J. Day
2007-09-05 10:02 ` Jan Engelhardt
2007-09-05 10:23 ` Robert P. J. Day
2007-09-05 20:11 ` Sam Ravnborg
2007-09-05 20:12 ` Sam Ravnborg
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=Pine.LNX.4.64.0709050509150.27539@localhost.localdomain \
--to=rpjday@mindspring.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
all inboxes | Powered by JetHome®