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]
Date:	Fri, 31 Aug 2007 18:30:44 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Valdis.Kletnieks@...edu
Cc:	Adrian Bunk <bunk@...nel.org>, Oliver Neukum <oliver@...kum.org>,
	linux-kernel@...r.kernel.org
Subject: Re: possible build system oddity

On Fri, Aug 31, 2007 at 11:00:27AM -0400, Valdis.Kletnieks@...edu wrote:
> On Fri, 31 Aug 2007 10:42:29 +0200, Adrian Bunk said:
> > On Fri, Aug 31, 2007 at 10:37:28AM +0200, Oliver Neukum wrote:
> > > Hi,
> > > 
> > > I only touched sound/usb/usbaudio.c
> > > Nevertheless the whole subtree und sound/ is recompiling. What's
> > > happening?
> > 
> > The only file that gets compiled (CC) should be sound/usb/usbaudio.c
> > 
> > It seems you are confused by the fact that this recompilation results in 
> > several relinks (LD)?
> 
> Or something else changed that he didn't realize.  Just the other day, I
> applied a one-line patch that hit one .c file, and *the entire kernel*
> started rebuilding.
> 
> Took me a while to figure out that I'd been looking for something else, and
> done a 'vi Makefile' in the top level, and exited with 'ZZ' rather than ':q' ;)

That should not result in a full rebuild, but you would see at least stuff in
kernel/ being compiled.

kbuild try to track all dependencies and sometimes people have a few suprises.
But the important part is that people *trust* that kbuild does the right thing
when they touch something - and so it is these days.

	Sam
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ