mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	Roman Zippel <zippel@linux-m68k.org>
Subject: Re: building a specific in-tree module is currently a bit broken
Date: Wed, 5 Sep 2007 05:42:38 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709050536410.31804@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0709051142080.5419@fbirervta.pbzchgretzou.qr>

On Wed, 5 Sep 2007, Jan Engelhardt wrote:

>
> On Sep 5 2007 11:37, Michal Piotrowski wrote:
> >
> >Hi,
> >
> >[Adding K{build,config} wizards to CC]
> >
> >On 05/09/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
> >>
> >> $ make distclean
> >> $ make defconfig
> >> $ make menuconfig      (select visor.ko to be built a module)
> >> $ make drivers/usb/serial/visor.ko
>
> Beep. Need 'make scripts prepare' between menuconfig and visor.

that doesn't solve the problem.  i should have mentioned that i
already (unnecessarily, i suggest) ran "make modules_prepare", but the
problem persists.

the issue seems to be that running that last make command to build the
module visor.ko doesn't somehow signal the Makefile that this is a
*module* build, and therefore no module-related initialization is
done, such as creating that directory or setting the Makefile variable
MODVERDIR, etc, etc.

once you've build at least one module successfully, then the directory
.tmp_versions exists so future module builds will work fine.  it's
only when you do a clean, *immediately* followed by trying to do an
in-tree module build, that this is going to bite you.

rday

-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://crashcourse.ca
========================================================================

  reply	other threads:[~2007-09-05  9:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05  9:16 Robert P. J. Day
2007-09-05  9:37 ` Michal Piotrowski
2007-09-05  9:43   ` Jan Engelhardt
2007-09-05  9:42     ` Robert P. J. Day [this message]
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.0709050536410.31804@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.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®