From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>
Cc: regressions@lists.linux.dev, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, "Petr Tesařík" <petr@tesarici.cz>
Subject: Re: [PATCH v1] docs: verify/bisect: fixes, finetuning, and support for Arch
Date: Wed, 6 Mar 2024 20:27:02 +0700 [thread overview]
Message-ID: <ZehvJv3fDZIPs9Kc@archie.me> (raw)
In-Reply-To: <6592c9ef4244faa484b4113f088dbc1beca61015.1709716794.git.linux@leemhuis.info>
[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]
On Wed, Mar 06, 2024 at 10:21:12AM +0100, Thorsten Leemhuis wrote:
> diff --git a/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst b/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> index 54bde8bac95c67..58211840ac6ffb 100644
> --- a/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> +++ b/Documentation/admin-guide/verify-bugs-and-bisect-regressions.rst
> @@ -192,8 +192,8 @@ will be considered the 'good' release and used to prepare the .config file.
>
> sudo rm -rf /lib/modules/6.0-rc1-local-gcafec0cacaca0
> sudo kernel-install -v remove 6.0-rc1-local-gcafec0cacaca0
> - # * Note, if kernel-install is missing, you will have to
> - # manually remove the kernel image and related files.
> + # * Note, on some distributions kernel-install is missing
> + # or does only part of the job.
Consult documentation of your distribution for how to manually install/remove
the kernel.
> Install build requirements
> --------------------------
> @@ -1076,72 +1078,103 @@ about to build.
> Here are a few examples what you typically need on some mainstream
> distributions:
>
> +* Arch Linux and derivatives::
> +
> + sudo pacman --needed -S bc binutils bison flex gcc git kmod libelf openssl \
> + pahole perl zlib ncurses qt6-base
> +
> * Debian, Ubuntu, and derivatives::
>
> - sudo apt install bc binutils bison dwarves flex gcc git make openssl \
> - pahole perl-base libssl-dev libelf-dev
> + sudo apt install bc binutils bison dwarves flex gcc git kmod libelf-dev \
> + libssl-dev make openssl pahole perl-base pkg-config zlib1g-dev \
> + libncurses-dev qt6-base-dev g++
>
> * Fedora and derivatives::
>
> - sudo dnf install binutils /usr/include/{libelf.h,openssl/pkcs7.h} \
> - /usr/bin/{bc,bison,flex,gcc,git,openssl,make,perl,pahole}
> + sudo dnf install binutils \
> + /usr/bin/{bc,bison,flex,gcc,git,openssl,make,perl,pahole,rpmbuild} \
> + /usr/include/{libelf.h,openssl/pkcs7.h,zlib.h,ncurses.h,qt6/QtGui/QAction}
IMO qt packages are for people who wish to do xconfig instead of menuconfig
or nconfig.
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-03-06 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 9:21 [PATCH v1] docs: verify/bisect: fixes, finetuning, and support for Arch Thorsten Leemhuis
2024-03-06 10:18 ` Petr Tesařík
2024-03-06 10:34 ` Thorsten Leemhuis
2024-03-06 13:27 ` Bagas Sanjaya [this message]
2024-03-07 8:56 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-09 6:54 ` Bagas Sanjaya
2024-03-07 11:40 ` Jonathan Corbet
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=ZehvJv3fDZIPs9Kc@archie.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=petr@tesarici.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).