From: Sam Ravnborg <sam@ravnborg.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.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 22:11:53 +0200 [thread overview]
Message-ID: <20070905201153.GB30812@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0709051142080.5419@fbirervta.pbzchgretzou.qr>
On Wed, Sep 05, 2007 at 11:43:15AM +0200, 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.
Nope - kbuild does this for you.
See following lines from top-level Makefile:
%.ko: prepare scripts FORCE
$(Q)$(MAKE) KBUILD_MODULES=$(if $(CONFIG_MODULES),1) \
$(build)=$(build-dir) $(@:.ko=.o)
$(Q)$(MAKE) -f $(srctree)/scripts/Makefile.modpost
But as pointed out it fails to create MODVERDIR.
I had one take on it some time ago and do not recall why I failed
to fix it. Should be trivial.
But this is a small issue that has been there for a long time
and is not -rc material. I will try to have it fixed for
next merge window.
Sam
next prev parent reply other threads:[~2007-09-05 20:10 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
2007-09-05 10:02 ` Jan Engelhardt
2007-09-05 10:23 ` Robert P. J. Day
2007-09-05 20:11 ` Sam Ravnborg [this message]
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=20070905201153.GB30812@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=rpjday@mindspring.com \
--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®