linux-kernel - Re: [PATCH v1] docs: describe how to quickly build Linux

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: <643054d9-5f96-b6d3-8ea4-a5feb9f094d7@leemhuis.info>
Date:   Sat, 25 Feb 2023 14:34:10 +0100
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Pavel Machek <pavel@....cz>
Cc:     Jonathan Corbet <corbet@....net>,
        Randy Dunlap <rdunlap@...radead.org>,
        Lukas Bulwahn <lukas.bulwahn@...il.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        regressions@...ts.linux.dev
Subject: Re: [PATCH v1] docs: describe how to quickly build Linux

On 25.02.23 10:29, Thorsten Leemhuis wrote:
> On 25.02.23 10:17, Pavel Machek wrote:
>
>>> +       mkdir ~/linux/ ~/linux/sources ~/linux/build
>>> +       git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git \
>>> +         ~/linux/sources
>>> +       cd ~/linux/sources/
>>> +       # hint: if you don't want to build any stable or longterm kernels, skip the
>>> +       #   next two commands
>>> +       git remote add linux-stable \
>>> +         https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>>> +       git fetch --all
>>> +       # hint: if you want to apply patches, do it at this point (see below for details)
>>> +       # hint: at this point it's recommended to tag your build (see below for details)
>>> +       yes "" | make O=~/linux/build/ localmodconfig
>>> +       # hint: at this point you might want or have to adjust the build configuration
>>> +       #  (see below for details)
>>> +       # note: if you are running a Debian kernel, you'll have to adjust the configuration
>>> +       #  at this point (see below)
>>> +       make -j $(nproc --all) O=~/linux/build/
>>
>> Is the complexity of using O= worth it for one-off kernel builds?
> 
> That is a good question. I seemed like the right thing to do when I
> started writing this guide (maybe just because I've been doing it that
> way for ages), but now that you ask I'm unsure myself.
> 
> /me wonders how others feel about it

/me should have pondered with the idea for more time before writing aboe
mail, because:

Having thought about this some more, I decided to drop it, the
complexity really is not worth it.

Many thx for the suggestion!

Ciao, Thorsten