linux-kernel - Re: building a specific in-tree module is currently a bit broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0709050536410.31804@localhost.localdomain>
Date:	Wed, 5 Sep 2007 05:42:38 -0400 (EDT)
From:	"Robert P. J. Day" <rpjday@...dspring.com>
To:	Jan Engelhardt <jengelh@...putergmbh.de>
cc:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Sam Ravnborg <sam@...nborg.org>,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: building a specific in-tree module is currently a bit broken

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@...dspring.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
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/