linux-kernel - Re: A question about compiling Linux kernel

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]

Message-ID: <9ae992fe-a3a9-8c1a-200b-3fe683d658a2@gmail.com>
Date:   Fri, 10 Mar 2023 09:21:12 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux Kernel Build System <linux-kbuild@...r.kernel.org>,
        Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: A question about compiling Linux kernel

On 3/10/23 04:22, Mirsad Goran Todorovac wrote:
> Hi Mr. Bagas,
> 
> If you can recall, you instructed me to use ccache, however with frequent rebuilds
> and especially bisects it would be better to recompile just the objects that have
> changed between the versions, rather than doing "make clean; make CC='ccache gcc'"
> 
> Is it safe to just do make CC='ccache gcc' and let make decide what to recompile?
> 

I have tried building a userspace application, for which the source code is
obtained by git. I do the initial build first, then git pull-ing without cleaning
the build directory, then incremental rebuild (usually `make` or `ninja`).
The incremental build only rebuild what is changed. However, when the version
identifier (mostly via build config) is changed, all previous build artifacts
are invalidated, essentially rebuild from scratch.

IMO, above can also be applied to Linux kernel (but I haven't tried to build
that way).

Cc: linux-kbuild list since I'm unsure on this.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara