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

Message-ID: <315b5e4a-43e7-f7af-f320-a5a3564127c6@alu.unizg.hr>
Date:   Thu, 9 Mar 2023 22:22:58 +0100
From:   Mirsad Goran Todorovac <mirsad.todorovac@....unizg.hr>
To:     Bagas Sanjaya <bagasdotme@...il.com>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: A question about compiling Linux kernel

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?

Normally I would experiment, but it is hard to predict what could happen with
63500 source files. Especially if .config is changed?

Of course "make clean" is obviously the safest way, but it might not be exactly
environmentally friendly :-)

I am not certain how git changes mtime and ctime when doing "git checkout <version>"?

Will make be able to handle this, or is it best to do a "make clean" and rebuild
from scratch. Possibly speeding up things with ccache ...

Thank you very much for all your support in the past months since August.

Best regards,
Mirsad

-- 
Mirsad Goran Todorovac
Sistem inženjer
Grafički fakultet | Akademija likovnih umjetnosti
Sveučilište u Zagrebu

System engineer
Faculty of Graphic Arts | Academy of Fine Arts
University of Zagreb, Republic of Croatia
The European Union