linux-kernel - Re: [PATCH][update] Makefile: allow no update .config build

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] [day] [month] [year] [list]

Date:	Fri, 29 Mar 2013 10:12:25 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	liguang <lig.fnst@...fujitsu.com>
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][update] Makefile: allow no update .config build

On 29.3.2013 01:46, liguang wrote:
> if we pull some commits from other git repo
> which bring in a few CONFIG_* options, then
> we have to build all again, but we do assure
> these options are not interesting for us,
> so the long waiting build will be offending.
> this change help us to avoid all-build.

scripts/basic/fixdep makes sure that only the affected parts are rebuild
when the config changes. Obviously, if a CONFIG_ option appears in a
widely used header file, the whole kernel is rebuilt. Otherwise object
files would be built with different versions of the header file. If you
want to shoot yourself in the foot and override this, then do a 'touch
include/config/*.conf', but please do not add such a hack to the Makefile.

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