All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH v1] docs: describe how to quickly build Linux
Date: Sat, 25 Feb 2023 10:17:26 +0100	[thread overview]
Message-ID: <Y/nSJvm6h4Sq5PR2@duo.ucw.cz> (raw)
In-Reply-To: <fabdb45fa44db2531f0dbe5e88545c49dfb87040.1675252073.git.linux@leemhuis.info>

[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]

Hi!

> +If your platform uses techniques like Secure Boot, prepare the system to permit
> +starting self-compiled Linux kernels; install compilers and everything else
> +needed for building Linux; make sure to have 15 Gigabyte free space in your home
> +directory. Now run the following commands to download the sources of Linux,
> +which you then use to configure, build and install your own
> kernel::

15GB is quite a lot. Maybe the shallow clone should be given another
chance?

> +       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?

Best regards,
								Pavel
-- 
People of Russia, stop Putin before his war on Ukraine escalates.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  parent reply	other threads:[~2023-02-25  9:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-01 11:52 [PATCH v1] docs: describe how to quickly build Linux Thorsten Leemhuis
2023-02-01 12:42 ` Greg KH
2023-02-01 12:44   ` Greg KH
2023-02-01 13:22     ` Thorsten Leemhuis
2023-02-01 14:02       ` Greg KH
2023-02-02 11:15 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-02-02 14:27   ` Greg KH
2023-02-02 14:57     ` Thorsten Leemhuis
2023-02-02 15:08   ` Konstantin Ryabitsev
2023-02-02 15:36     ` Thorsten Leemhuis
2023-02-03  9:44       ` Jani Nikula
2023-02-03  9:52         ` Thorsten Leemhuis
2023-02-10 11:38   ` Thorsten Leemhuis
2023-02-10 13:55     ` Konstantin Ryabitsev
2023-02-25  9:17 ` Pavel Machek [this message]
2023-02-25  9:29   ` Thorsten Leemhuis
2023-02-25 13:34     ` Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y/nSJvm6h4Sq5PR2@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=lukas.bulwahn@gmail.com \
    --cc=rdunlap@infradead.org \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.