2016-09-19 11:07:56 +00:00
|
|
|
.. _changes:
|
|
|
|
|
|
2016-10-26 22:34:09 +00:00
|
|
|
Minimal requirements to compile the Kernel
|
2016-09-19 11:07:42 +00:00
|
|
|
++++++++++++++++++++++++++++++++++++++++++
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Intro
|
|
|
|
|
=====
|
|
|
|
|
|
|
|
|
|
This document is designed to provide a list of the minimum levels of
|
2022-04-19 14:48:52 +00:00
|
|
|
software necessary to run the current kernel version.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
This document is originally based on my "Changes" file for 2.0.x kernels
|
|
|
|
|
and therefore owes credit to the same people as that file (Jared Mauch,
|
|
|
|
|
Axel Boldt, Alessandro Sigala, and countless other users all over the
|
|
|
|
|
'net).
|
|
|
|
|
|
|
|
|
|
Current Minimal Requirements
|
2016-09-19 11:07:42 +00:00
|
|
|
****************************
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
Upgrade to at **least** these software revisions before thinking you've
|
2005-04-16 22:20:36 +00:00
|
|
|
encountered a bug! If you're unsure what version you're currently
|
|
|
|
|
running, the suggested command should tell you.
|
|
|
|
|
|
2011-07-11 23:48:38 +00:00
|
|
|
Again, keep in mind that this list assumes you are already functionally
|
|
|
|
|
running a Linux kernel. Also, not all tools are necessary on all
|
2019-04-18 20:43:36 +00:00
|
|
|
systems; obviously, if you don't have any PC Card hardware, for example,
|
|
|
|
|
you probably needn't concern yourself with pcmciautils.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
====================== =============== ========================================
|
|
|
|
|
Program Minimal version Command to check the version
|
|
|
|
|
====================== =============== ========================================
|
2021-09-10 23:40:38 +00:00
|
|
|
GNU C 5.1 gcc --version
|
Documentation: Raise the minimum supported version of LLVM to 11.0.0
LLVM versions prior to 11.0.0 have a harder time with dead code
elimination, which can cause issues with commonly used expressions such
as BUILD_BUG_ON and the bitmask functions/macros in bitfield.h (see the
first two issues links below).
Whenever there is an issue within LLVM that has been resolved in a later
release, the only course of action is to gate the problematic
configuration or source code on the toolchain verson or raise the
minimum supported version of LLVM for building the kernel, as LLVM has a
limited support lifetime compared to GCC. GCC major releases will
typically see a few point releases across a two year period on average
whereas LLVM major releases are only supported until the next major
release and will only see one or two point releases within that
timeframe. For example, GCC 8.1 was released in May 2018 and GCC 8.5 was
released in May 2021, whereas LLVM 12.0.0 was released in April 2021 and
its only point release, 12.0.1, was released in July 2021, giving a
minimal window for fixes to be backported.
To resolve these build errors around improper dead code elimination,
raise the minimum supported version of LLVM for building the kernel to
11.0.0. Doing so is a more proper solution than mucking around with core
kernel macros that have always worked with GCC or disabling drivers for
using these macros in a proper manner. This type of issue may continue
to crop up and require patching, which creates more debt for bumping the
minimum supported version in the future.
This should have a minimal impact to distributions. Using a script to
pull several different Docker images and check the output of
'clang --version':
archlinux:latest: clang version 13.0.0
debian:oldoldstable-slim: clang version 3.8.1-24 (tags/RELEASE_381/final)
debian:oldstable-slim: clang version 7.0.1-8+deb10u2 (tags/RELEASE_701/final)
debian:stable-slim: Debian clang version 11.0.1-2
debian:testing-slim: Debian clang version 11.1.0-4
debian:unstable-slim: Debian clang version 11.1.0-4
fedora:34: clang version 12.0.1 (Fedora 12.0.1-1.fc34)
fedora:latest: clang version 13.0.0 (Fedora 13.0.0-3.fc35)
fedora:rawhide: clang version 13.0.0 (Fedora 13.0.0-5.fc36)
opensuse/leap:15.2: clang version 9.0.1
opensuse/leap:latest: clang version 11.0.1
opensuse/tumbleweed:latest: clang version 13.0.0
ubuntu:bionic: clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
ubuntu:latest: clang version 10.0.0-4ubuntu1
ubuntu:hirsute: Ubuntu clang version 12.0.0-3ubuntu1~21.04.2
ubuntu:rolling: Ubuntu clang version 13.0.0-2
ubuntu:devel: Ubuntu clang version 13.0.0-9
In every case, the distribution's version of clang is either older than
the current minimum supported version of LLVM 10.0.1 or equal to or
greater than the proposed 11.0.0 so nothing should change.
Another benefit of this change is LLVM=1 works better with arm64 and
x86_64 since commit f12b034afeb3 ("scripts/Makefile.clang: default to
LLVM_IAS=1") enabled the integrated assembler by default, which only
works well with clang 11+ (clang-10 required it to be disabled to
successfully build a kernel).
Link: https://github.com/ClangBuiltLinux/linux/issues/1293
Link: https://github.com/ClangBuiltLinux/linux/issues/1506
Link: https://github.com/ClangBuiltLinux/linux/issues/1511
Link: https://github.com/llvm/llvm-project/commit/fa496ce3c6774097080c8a9cb808da56f383b938
Link: https://groups.google.com/g/clang-built-linux/c/mPQb9_ZWW0s/m/W7o6S-QTBAAJ
Link: https://github.com/ClangBuiltLinux/misc-scripts
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
Reviewed-by: Mark Brown <broonie@kernel.org>
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2021-11-29 16:57:58 +00:00
|
|
|
Clang/LLVM (optional) 11.0.0 clang --version
|
rust: upgrade to Rust 1.68.2
This is the first upgrade to the Rust toolchain since the initial Rust
merge, from 1.62.0 to 1.68.2 (i.e. the latest).
# Context
The kernel currently supports only a single Rust version [1] (rather
than a minimum) given our usage of some "unstable" Rust features [2]
which do not promise backwards compatibility.
The goal is to reach a point where we can declare a minimum version for
the toolchain. For instance, by waiting for some of the features to be
stabilized. Therefore, the first minimum Rust version that the kernel
will support is "in the future".
# Upgrade policy
Given we will eventually need to reach that minimum version, it would be
ideal to upgrade the compiler from time to time to be as close as
possible to that goal and find any issues sooner. In the extreme, we
could upgrade as soon as a new Rust release is out. Of course, upgrading
so often is in stark contrast to what one normally would need for GCC
and LLVM, especially given the release schedule: 6 weeks for Rust vs.
half a year for LLVM and a year for GCC.
Having said that, there is no particular advantage to updating slowly
either: kernel developers in "stable" distributions are unlikely to be
able to use their distribution-provided Rust toolchain for the kernel
anyway [3]. Instead, by routinely upgrading to the latest instead,
kernel developers using Linux distributions that track the latest Rust
release may be able to use those rather than Rust-provided ones,
especially if their package manager allows to pin / hold back /
downgrade the version for some days during windows where the version may
not match. For instance, Arch, Fedora, Gentoo and openSUSE all provide
and track the latest version of Rust as they get released every 6 weeks.
Then, when the minimum version is reached, we will stop upgrading and
decide how wide the window of support will be. For instance, a year of
Rust versions. We will probably want to start small, and then widen it
over time, just like the kernel did originally for LLVM, see commit
3519c4d6e08e ("Documentation: add minimum clang/llvm version").
# Unstable features stabilized
This upgrade allows us to remove the following unstable features since
they were stabilized:
- `feature(explicit_generic_args_with_impl_trait)` (1.63).
- `feature(core_ffi_c)` (1.64).
- `feature(generic_associated_types)` (1.65).
- `feature(const_ptr_offset_from)` (1.65, *).
- `feature(bench_black_box)` (1.66, *).
- `feature(pin_macro)` (1.68).
The ones marked with `*` apply only to our old `rust` branch, not
mainline yet, i.e. only for code that we may potentially upstream.
With this patch applied, the only unstable feature allowed to be used
outside the `kernel` crate is `new_uninit`, though other code to be
upstreamed may increase the list.
Please see [2] for details.
# Other required changes
Since 1.63, `rustdoc` triggers the `broken_intra_doc_links` lint for
links pointing to exported (`#[macro_export]`) `macro_rules`. An issue
was opened upstream [4], but it turns out it is intended behavior. For
the moment, just add an explicit reference for each link. Later we can
revisit this if `rustdoc` removes the compatibility measure.
Nevertheless, this was helpful to discover a link that was pointing to
the wrong place unintentionally. Since that one was actually wrong, it
is fixed in a previous commit independently.
Another change was the addition of `cfg(no_rc)` and `cfg(no_sync)` in
upstream [5], thus remove our original changes for that.
Similarly, upstream now tests that it compiles successfully with
`#[cfg(not(no_global_oom_handling))]` [6], which allow us to get rid
of some changes, such as an `#[allow(dead_code)]`.
In addition, remove another `#[allow(dead_code)]` due to new uses
within the standard library.
Finally, add `try_extend_trusted` and move the code in `spec_extend.rs`
since upstream moved it for the infallible version.
# `alloc` upgrade and reviewing
There are a large amount of changes, but the vast majority of them are
due to our `alloc` fork being upgraded at once.
There are two kinds of changes to be aware of: the ones coming from
upstream, which we should follow as closely as possible, and the updates
needed in our added fallible APIs to keep them matching the newer
infallible APIs coming from upstream.
Instead of taking a look at the diff of this patch, an alternative
approach is reviewing a diff of the changes between upstream `alloc` and
the kernel's. This allows to easily inspect the kernel additions only,
especially to check if the fallible methods we already have still match
the infallible ones in the new version coming from upstream.
Another approach is reviewing the changes introduced in the additions in
the kernel fork between the two versions. This is useful to spot
potentially unintended changes to our additions.
To apply these approaches, one may follow steps similar to the following
to generate a pair of patches that show the differences between upstream
Rust and the kernel (for the subset of `alloc` we use) before and after
applying this patch:
# Get the difference with respect to the old version.
git -C rust checkout $(linux/scripts/min-tool-version.sh rustc)
git -C linux ls-tree -r --name-only HEAD -- rust/alloc |
cut -d/ -f3- |
grep -Fv README.md |
xargs -IPATH cp rust/library/alloc/src/PATH linux/rust/alloc/PATH
git -C linux diff --patch-with-stat --summary -R > old.patch
git -C linux restore rust/alloc
# Apply this patch.
git -C linux am rust-upgrade.patch
# Get the difference with respect to the new version.
git -C rust checkout $(linux/scripts/min-tool-version.sh rustc)
git -C linux ls-tree -r --name-only HEAD -- rust/alloc |
cut -d/ -f3- |
grep -Fv README.md |
xargs -IPATH cp rust/library/alloc/src/PATH linux/rust/alloc/PATH
git -C linux diff --patch-with-stat --summary -R > new.patch
git -C linux restore rust/alloc
Now one may check the `new.patch` to take a look at the additions (first
approach) or at the difference between those two patches (second
approach). For the latter, a side-by-side tool is recommended.
Link: https://rust-for-linux.com/rust-version-policy [1]
Link: https://github.com/Rust-for-Linux/linux/issues/2 [2]
Link: https://lore.kernel.org/rust-for-linux/CANiq72mT3bVDKdHgaea-6WiZazd8Mvurqmqegbe5JZxVyLR8Yg@mail.gmail.com/ [3]
Link: https://github.com/rust-lang/rust/issues/106142 [4]
Link: https://github.com/rust-lang/rust/pull/89891 [5]
Link: https://github.com/rust-lang/rust/pull/98652 [6]
Reviewed-by: Björn Roy Baron <bjorn3_gh@protonmail.com>
Reviewed-by: Gary Guo <gary@garyguo.net>
Reviewed-By: Martin Rodriguez Reboredo <yakoyoku@gmail.com>
Tested-by: Ariel Miculas <amiculas@cisco.com>
Tested-by: David Gow <davidgow@google.com>
Tested-by: Boqun Feng <boqun.feng@gmail.com>
Link: https://lore.kernel.org/r/20230418214347.324156-4-ojeda@kernel.org
[ Removed `feature(core_ffi_c)` from `uapi` ]
Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
2023-04-18 21:43:47 +00:00
|
|
|
Rust (optional) 1.68.2 rustc --version
|
2021-07-03 15:23:16 +00:00
|
|
|
bindgen (optional) 0.56.0 bindgen --version
|
2022-10-01 20:28:35 +00:00
|
|
|
GNU make 3.82 make --version
|
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 01:11:00 +00:00
|
|
|
bash 4.2 bash --version
|
2022-10-12 18:18:41 +00:00
|
|
|
binutils 2.25 ld -v
|
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-09 16:02:29 +00:00
|
|
|
flex 2.5.35 flex --version
|
|
|
|
|
bison 2.0 bison --version
|
2021-11-19 18:56:03 +00:00
|
|
|
pahole 1.16 pahole --version
|
2016-09-19 11:07:42 +00:00
|
|
|
util-linux 2.10o fdformat --version
|
2018-07-02 02:46:06 +00:00
|
|
|
kmod 13 depmod -V
|
2016-09-19 11:07:42 +00:00
|
|
|
e2fsprogs 1.41.4 e2fsck -V
|
|
|
|
|
jfsutils 1.1.3 fsck.jfs -V
|
|
|
|
|
reiserfsprogs 3.6.3 reiserfsck -V
|
|
|
|
|
xfsprogs 2.6.0 xfs_db -V
|
|
|
|
|
squashfs-tools 4.0 mksquashfs -version
|
|
|
|
|
btrfs-progs 0.18 btrfsck
|
|
|
|
|
pcmciautils 004 pccardctl -V
|
|
|
|
|
quota-tools 3.09 quota -V
|
|
|
|
|
PPP 2.4.0 pppd --version
|
|
|
|
|
nfs-utils 1.0.5 showmount --version
|
|
|
|
|
procps 3.2.0 ps --version
|
|
|
|
|
udev 081 udevd --version
|
|
|
|
|
grub 0.93 grub --version || grub-install --version
|
|
|
|
|
mcelog 0.6 mcelog --version
|
|
|
|
|
iptables 1.4.2 iptables -V
|
|
|
|
|
openssl & libcrypto 1.0.0 openssl version
|
|
|
|
|
bc 1.06.95 bc --version
|
2021-11-10 09:16:48 +00:00
|
|
|
Sphinx\ [#f1]_ 1.7 sphinx-build --version
|
2022-04-19 14:48:15 +00:00
|
|
|
cpio any cpio --version
|
2023-05-21 13:23:36 +00:00
|
|
|
GNU tar 1.28 tar --version
|
2023-05-15 17:32:17 +00:00
|
|
|
gtags (optional) 6.6.5 gtags --version
|
2016-09-19 11:07:42 +00:00
|
|
|
====================== =============== ========================================
|
2009-12-14 13:52:10 +00:00
|
|
|
|
2016-09-19 11:07:43 +00:00
|
|
|
.. [#f1] Sphinx is needed only to build the Kernel documentation
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Kernel compilation
|
2016-09-19 11:07:42 +00:00
|
|
|
******************
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
GCC
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
The gcc version requirements may vary depending on the type of CPU in your
|
2006-01-08 09:04:09 +00:00
|
|
|
computer.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-08-26 19:15:55 +00:00
|
|
|
Clang/LLVM (optional)
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
The latest formal release of clang and LLVM utils (according to
|
|
|
|
|
`releases.llvm.org <https://releases.llvm.org>`_) are supported for building
|
|
|
|
|
kernels. Older releases aren't guaranteed to work, and we may drop workarounds
|
|
|
|
|
from the kernel that were used to support older versions. Please see additional
|
|
|
|
|
docs on :ref:`Building Linux with Clang/LLVM <kbuild_llvm>`.
|
|
|
|
|
|
2021-07-03 15:23:16 +00:00
|
|
|
Rust (optional)
|
|
|
|
|
---------------
|
|
|
|
|
|
|
|
|
|
A particular version of the Rust toolchain is required. Newer versions may or
|
|
|
|
|
may not work because the kernel depends on some unstable Rust features, for
|
|
|
|
|
the moment.
|
|
|
|
|
|
|
|
|
|
Each Rust toolchain comes with several "components", some of which are required
|
|
|
|
|
(like ``rustc``) and some that are optional. The ``rust-src`` component (which
|
|
|
|
|
is optional) needs to be installed to build the kernel. Other components are
|
|
|
|
|
useful for developing.
|
|
|
|
|
|
|
|
|
|
Please see Documentation/rust/quick-start.rst for instructions on how to
|
|
|
|
|
satisfy the build requirements of Rust support. In particular, the ``Makefile``
|
|
|
|
|
target ``rustavailable`` is useful to check why the Rust toolchain may not
|
|
|
|
|
be detected.
|
|
|
|
|
|
|
|
|
|
bindgen (optional)
|
|
|
|
|
------------------
|
|
|
|
|
|
|
|
|
|
``bindgen`` is used to generate the Rust bindings to the C side of the kernel.
|
|
|
|
|
It depends on ``libclang``.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Make
|
|
|
|
|
----
|
|
|
|
|
|
2022-10-01 20:28:35 +00:00
|
|
|
You will need GNU make 3.82 or later to build the kernel.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 01:11:00 +00:00
|
|
|
Bash
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
Some bash scripts are used for the kernel build.
|
|
|
|
|
Bash 4.2 or newer is needed.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Binutils
|
|
|
|
|
--------
|
|
|
|
|
|
2022-10-12 18:18:41 +00:00
|
|
|
Binutils 2.25 or newer is needed to build the kernel.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-06-28 23:39:50 +00:00
|
|
|
pkg-config
|
|
|
|
|
----------
|
|
|
|
|
|
|
|
|
|
The build system, as of 4.18, requires pkg-config to check for installed
|
|
|
|
|
kconfig tools and to determine flags settings for use in
|
kconfig: do not require pkg-config on make {menu,n}config
Meelis Roos reported a {menu,n}config regression:
"I have libncurses devel package installed in the default system
location (as do 99%+ on actual developers probably) and in this
case, pkg-config is useless. pkg-config is needed only when
libraries and headers are installed in non-default locations but
it is bad to require installation of pkg-config on all the machines
where make menuconfig would be possibly run."
For {menu,n}config, do not use pkg-config if it is not installed.
For {g,x}config, keep checking pkg-config since we really rely on it
for finding the installation paths of the required packages.
Fixes: 4ab3b80159d4 ("kconfig: check for pkg-config on make {menu,n,g,x}config")
Reported-by: Meelis Roos <mroos@linux.ee>
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Tested-by: Meelis Roos <mroos@linux.ee>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
2018-08-31 09:34:55 +00:00
|
|
|
'make {g,x}config'. Previously pkg-config was being used but not
|
2018-06-28 23:39:50 +00:00
|
|
|
verified or documented.
|
|
|
|
|
|
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-09 16:02:29 +00:00
|
|
|
Flex
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
Since Linux 4.16, the build system generates lexical analyzers
|
|
|
|
|
during build. This requires flex 2.5.35 or later.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bison
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
|
|
Since Linux 4.16, the build system generates parsers
|
|
|
|
|
during build. This requires bison 2.0 or later.
|
|
|
|
|
|
2021-11-19 18:56:03 +00:00
|
|
|
pahole:
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
Since Linux 5.2, if CONFIG_DEBUG_INFO_BTF is selected, the build system
|
|
|
|
|
generates BTF (BPF Type Format) from DWARF in vmlinux, a bit later from kernel
|
|
|
|
|
modules as well. This requires pahole v1.16 or later.
|
|
|
|
|
|
|
|
|
|
It is found in the 'dwarves' or 'pahole' distro packages or from
|
|
|
|
|
https://fedorapeople.org/~acme/dwarves/.
|
|
|
|
|
|
2009-06-17 23:26:30 +00:00
|
|
|
Perl
|
|
|
|
|
----
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
You will need perl 5 and the following modules: ``Getopt::Long``,
|
|
|
|
|
``Getopt::Std``, ``File::Basename``, and ``File::Find`` to build the kernel.
|
2009-06-17 23:26:30 +00:00
|
|
|
|
2014-05-19 13:02:17 +00:00
|
|
|
BC
|
|
|
|
|
--
|
|
|
|
|
|
|
|
|
|
You will need bc to build kernels 3.10 and higher
|
|
|
|
|
|
2009-06-17 23:26:30 +00:00
|
|
|
|
2015-08-27 10:13:36 +00:00
|
|
|
OpenSSL
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
Module signing and external certificate handling use the OpenSSL program and
|
|
|
|
|
crypto library to do key creation and signature generation.
|
|
|
|
|
|
|
|
|
|
You will need openssl to build kernels 3.7 and higher if module signing is
|
|
|
|
|
enabled. You will also need openssl development packages to build kernels 4.3
|
|
|
|
|
and higher.
|
|
|
|
|
|
2023-05-21 13:23:36 +00:00
|
|
|
Tar
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
GNU tar is needed if you want to enable access to the kernel headers via sysfs
|
|
|
|
|
(CONFIG_IKHEADERS).
|
|
|
|
|
|
2023-05-15 17:32:17 +00:00
|
|
|
gtags / GNU GLOBAL (optional)
|
|
|
|
|
-----------------------------
|
|
|
|
|
|
|
|
|
|
The kernel build requires GNU GLOBAL version 6.6.5 or later to generate
|
|
|
|
|
tag files through ``make gtags``. This is due to its use of the gtags
|
|
|
|
|
``-C (--directory)`` flag.
|
2015-08-27 10:13:36 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
System utilities
|
2016-09-19 11:07:42 +00:00
|
|
|
****************
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Architectural changes
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
DevFS has been obsoleted in favour of udev
|
2020-06-21 13:36:30 +00:00
|
|
|
(https://www.kernel.org/pub/linux/utils/kernel/hotplug/)
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
32-bit UID support is now in place. Have fun!
|
|
|
|
|
|
|
|
|
|
Linux documentation for functions is transitioning to inline
|
|
|
|
|
documentation via specially-formatted comments near their
|
2017-05-14 14:50:11 +00:00
|
|
|
definitions in the source. These comments can be combined with ReST
|
|
|
|
|
files the Documentation/ directory to make enriched documentation, which can
|
|
|
|
|
then be converted to PostScript, HTML, LaTex, ePUB and PDF files.
|
|
|
|
|
In order to convert from ReST format to a format of your choice, you'll need
|
|
|
|
|
Sphinx.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Util-linux
|
|
|
|
|
----------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
New versions of util-linux provide ``fdisk`` support for larger disks,
|
2005-04-16 22:20:36 +00:00
|
|
|
support new options to mount, recognize more supported partition
|
|
|
|
|
types, have a fdformat which works with 2.4 kernels, and similar goodies.
|
|
|
|
|
You'll probably want to upgrade.
|
|
|
|
|
|
|
|
|
|
Ksymoops
|
|
|
|
|
--------
|
|
|
|
|
|
2005-11-07 09:01:03 +00:00
|
|
|
If the unthinkable happens and your kernel oopses, you may need the
|
|
|
|
|
ksymoops tool to decode it, but in most cases you don't.
|
2016-09-19 11:07:42 +00:00
|
|
|
It is generally preferred to build the kernel with ``CONFIG_KALLSYMS`` so
|
2011-07-11 23:48:38 +00:00
|
|
|
that it produces readable dumps that can be used as-is (this also
|
|
|
|
|
produces better output than ksymoops). If for some reason your kernel
|
2016-09-19 11:07:42 +00:00
|
|
|
is not build with ``CONFIG_KALLSYMS`` and you have no way to rebuild and
|
2011-07-11 23:48:38 +00:00
|
|
|
reproduce the Oops with that option, then you can still decode that Oops
|
|
|
|
|
with ksymoops.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Mkinitrd
|
|
|
|
|
--------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
These changes to the ``/lib/modules`` file tree layout also require that
|
2005-04-16 22:20:36 +00:00
|
|
|
mkinitrd be upgraded.
|
|
|
|
|
|
|
|
|
|
E2fsprogs
|
|
|
|
|
---------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
The latest version of ``e2fsprogs`` fixes several bugs in fsck and
|
2005-04-16 22:20:36 +00:00
|
|
|
debugfs. Obviously, it's a good idea to upgrade.
|
|
|
|
|
|
|
|
|
|
JFSutils
|
|
|
|
|
--------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
The ``jfsutils`` package contains the utilities for the file system.
|
2005-04-16 22:20:36 +00:00
|
|
|
The following utilities are available:
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- ``fsck.jfs`` - initiate replay of the transaction log, and check
|
2005-04-16 22:20:36 +00:00
|
|
|
and repair a JFS formatted partition.
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- ``mkfs.jfs`` - create a JFS formatted partition.
|
|
|
|
|
|
|
|
|
|
- other file system utilities are also available in this package.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Reiserfsprogs
|
|
|
|
|
-------------
|
|
|
|
|
|
|
|
|
|
The reiserfsprogs package should be used for reiserfs-3.6.x
|
|
|
|
|
(Linux kernels 2.4.x). It is a combined package and contains working
|
2016-09-19 11:07:42 +00:00
|
|
|
versions of ``mkreiserfs``, ``resize_reiserfs``, ``debugreiserfs`` and
|
|
|
|
|
``reiserfsck``. These utils work on both i386 and alpha platforms.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Xfsprogs
|
|
|
|
|
--------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
The latest version of ``xfsprogs`` contains ``mkfs.xfs``, ``xfs_db``, and the
|
|
|
|
|
``xfs_repair`` utilities, among others, for the XFS filesystem. It is
|
2005-04-16 22:20:36 +00:00
|
|
|
architecture independent and any version from 2.0.0 onward should
|
|
|
|
|
work correctly with this version of the XFS kernel code (2.6.0 or
|
|
|
|
|
later is recommended, due to some significant improvements).
|
|
|
|
|
|
2005-06-27 23:28:45 +00:00
|
|
|
PCMCIAutils
|
|
|
|
|
-----------
|
|
|
|
|
|
2016-09-19 11:07:42 +00:00
|
|
|
PCMCIAutils replaces ``pcmcia-cs``. It properly sets up
|
2005-06-27 23:28:45 +00:00
|
|
|
PCMCIA sockets at system startup and loads the appropriate modules
|
|
|
|
|
for 16-bit PCMCIA devices if the kernel is modularized and the hotplug
|
|
|
|
|
subsystem is used.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Quota-tools
|
|
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
Support for 32 bit uid's and gid's is required if you want to use
|
|
|
|
|
the newer version 2 quota format. Quota-tools version 3.07 and
|
|
|
|
|
newer has this support. Use the recommended version or newer
|
|
|
|
|
from the table above.
|
|
|
|
|
|
|
|
|
|
Intel IA32 microcode
|
|
|
|
|
--------------------
|
|
|
|
|
|
|
|
|
|
A driver has been added to allow updating of Intel IA32 microcode,
|
2005-06-21 04:15:16 +00:00
|
|
|
accessible as a normal (misc) character device. If you are not using
|
2016-09-21 00:46:36 +00:00
|
|
|
udev you may need to::
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
mkdir /dev/cpu
|
|
|
|
|
mknod /dev/cpu/microcode c 10 184
|
|
|
|
|
chmod 0644 /dev/cpu/microcode
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
as root before you can use this. You'll probably also want to
|
|
|
|
|
get the user-space microcode_ctl utility to use with this.
|
|
|
|
|
|
|
|
|
|
udev
|
|
|
|
|
----
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
``udev`` is a userspace application for populating ``/dev`` dynamically with
|
|
|
|
|
only entries for devices actually present. ``udev`` replaces the basic
|
2006-11-30 04:32:19 +00:00
|
|
|
functionality of devfs, while allowing persistent device naming for
|
2005-06-21 04:15:16 +00:00
|
|
|
devices.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-09-28 04:45:20 +00:00
|
|
|
FUSE
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
Needs libfuse 2.4.0 or later. Absolute minimum is 2.3.0 but mount
|
2016-09-19 11:07:42 +00:00
|
|
|
options ``direct_io`` and ``kernel_cache`` won't work.
|
2005-09-28 04:45:20 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Networking
|
2016-09-19 11:07:42 +00:00
|
|
|
**********
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
General changes
|
|
|
|
|
---------------
|
|
|
|
|
|
|
|
|
|
If you have advanced network configuration needs, you should probably
|
|
|
|
|
consider using the network tools from ip-route2.
|
|
|
|
|
|
|
|
|
|
Packet Filter / NAT
|
|
|
|
|
-------------------
|
|
|
|
|
The packet filtering and NAT code uses the same tools like the previous 2.4.x
|
|
|
|
|
kernel series (iptables). It still includes backwards-compatibility modules
|
|
|
|
|
for 2.2.x-style ipchains and 2.0.x-style ipfwadm.
|
|
|
|
|
|
|
|
|
|
PPP
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
The PPP driver has been restructured to support multilink and to
|
|
|
|
|
enable it to operate over diverse media layers. If you use PPP,
|
|
|
|
|
upgrade pppd to at least 2.4.0.
|
|
|
|
|
|
2005-06-21 04:15:16 +00:00
|
|
|
If you are not using udev, you must have the device file /dev/ppp
|
2016-09-21 00:46:36 +00:00
|
|
|
which can be made by::
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
mknod /dev/ppp c 108 0
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
as root.
|
|
|
|
|
|
|
|
|
|
NFS-utils
|
|
|
|
|
---------
|
|
|
|
|
|
2011-07-11 23:48:38 +00:00
|
|
|
In ancient (2.4 and earlier) kernels, the nfs server needed to know
|
|
|
|
|
about any client that expected to be able to access files via NFS. This
|
2016-09-19 11:07:42 +00:00
|
|
|
information would be given to the kernel by ``mountd`` when the client
|
|
|
|
|
mounted the filesystem, or by ``exportfs`` at system startup. exportfs
|
|
|
|
|
would take information about active clients from ``/var/lib/nfs/rmtab``.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
This approach is quite fragile as it depends on rmtab being correct
|
|
|
|
|
which is not always easy, particularly when trying to implement
|
2016-09-19 11:07:42 +00:00
|
|
|
fail-over. Even when the system is working well, ``rmtab`` suffers from
|
2005-04-16 22:20:36 +00:00
|
|
|
getting lots of old entries that never get removed.
|
|
|
|
|
|
2011-07-11 23:48:38 +00:00
|
|
|
With modern kernels we have the option of having the kernel tell mountd
|
|
|
|
|
when it gets a request from an unknown host, and mountd can give
|
|
|
|
|
appropriate export information to the kernel. This removes the
|
2016-09-19 11:07:42 +00:00
|
|
|
dependency on ``rmtab`` and means that the kernel only needs to know about
|
2011-07-11 23:48:38 +00:00
|
|
|
currently active clients.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2016-09-21 00:46:36 +00:00
|
|
|
To enable this new functionality, you need to::
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2006-09-11 16:39:19 +00:00
|
|
|
mount -t nfsd nfsd /proc/fs/nfsd
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
before running exportfs or mountd. It is recommended that all NFS
|
|
|
|
|
services be protected from the internet-at-large by a firewall where
|
|
|
|
|
that is possible.
|
|
|
|
|
|
2009-04-28 21:37:02 +00:00
|
|
|
mcelog
|
|
|
|
|
------
|
|
|
|
|
|
2014-07-12 16:54:52 +00:00
|
|
|
On x86 kernels the mcelog utility is needed to process and log machine check
|
2016-09-19 11:07:42 +00:00
|
|
|
events when ``CONFIG_X86_MCE`` is enabled. Machine check events are errors
|
|
|
|
|
reported by the CPU. Processing them is strongly encouraged.
|
2009-04-28 21:37:02 +00:00
|
|
|
|
2016-09-19 11:07:43 +00:00
|
|
|
Kernel documentation
|
|
|
|
|
********************
|
|
|
|
|
|
|
|
|
|
Sphinx
|
|
|
|
|
------
|
|
|
|
|
|
2018-11-21 00:35:19 +00:00
|
|
|
Please see :ref:`sphinx_install` in :ref:`Documentation/doc-guide/sphinx.rst <sphinxdoc>`
|
2017-07-14 16:41:17 +00:00
|
|
|
for details about Sphinx requirements.
|
2016-09-19 11:07:43 +00:00
|
|
|
|
2021-07-03 15:23:16 +00:00
|
|
|
rustdoc
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
``rustdoc`` is used to generate the documentation for Rust code. Please see
|
|
|
|
|
Documentation/rust/general-information.rst for more information.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Getting updated software
|
|
|
|
|
========================
|
|
|
|
|
|
|
|
|
|
Kernel compilation
|
|
|
|
|
******************
|
|
|
|
|
|
2006-01-08 09:04:09 +00:00
|
|
|
gcc
|
|
|
|
|
---
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <ftp://ftp.gnu.org/gnu/gcc/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2020-08-26 19:15:55 +00:00
|
|
|
Clang/LLVM
|
|
|
|
|
----------
|
|
|
|
|
|
|
|
|
|
- :ref:`Getting LLVM <getting_llvm>`.
|
|
|
|
|
|
2021-07-03 15:23:16 +00:00
|
|
|
Rust
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
- Documentation/rust/quick-start.rst.
|
|
|
|
|
|
|
|
|
|
bindgen
|
|
|
|
|
-------
|
|
|
|
|
|
|
|
|
|
- Documentation/rust/quick-start.rst.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Make
|
|
|
|
|
----
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <ftp://ftp.gnu.org/gnu/make/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
scripts/check-local-export: avoid 'wait $!' for process substitution
Bash 4.4, released in 2016, supports 'wait $!' to check the exit status
of a process substitution, but it seems too new.
Some people using older bash versions (on CentOS 7, Ubuntu 16.04, etc.)
reported an error like this:
./scripts/check-local-export: line 54: wait: pid 17328 is not a child of this shell
I used the process substitution to avoid a pipeline, which executes each
command in a subshell. If the while-loop is executed in the subshell
context, variable changes within are lost after the subshell terminates.
Fortunately, Bash 4.2, released in 2011, supports the 'lastpipe' option,
which makes the last element of a pipeline run in the current shell process.
Switch to the pipeline with 'lastpipe' solution, and also set 'pipefail'
to catch errors from ${NM}.
Add the bash requirement to Documentation/process/changes.rst.
Fixes: 31cb50b5590f ("kbuild: check static EXPORT_SYMBOL* by script instead of modpost")
Reported-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Reported-by: Michael Ellerman <mpe@ellerman.id.au>
Reported-by: Wang Yugui <wangyugui@e16-tech.com>
Tested-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Acked-by: Nick Desaulniers <ndesaulniers@google.com>
Tested-by: Sedat Dilek <sedat.dilek@gmail.com> # LLVM-14 (x86-64)
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
2022-06-08 01:11:00 +00:00
|
|
|
Bash
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
- <ftp://ftp.gnu.org/gnu/bash/>
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Binutils
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2017-03-27 13:05:34 +00:00
|
|
|
- <https://www.kernel.org/pub/linux/devel/binutils/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
kbuild: prepare to remove C files pre-generated by flex and bison
In Linux build system convention, pre-generated files are version-
controlled with a "_shipped" suffix. During the kernel building,
they are simply shipped (copied) removing the suffix.
This approach can reduce external tool dependency for the kernel build,
but it is tedious to manually regenerate such artifacts from developers'
point of view. (We need to do "make REGENERATE_PARSERS=1" every time
we touch real source files such as *.l, *.y)
Some months ago, I sent out RFC patches to run flex, bison, and gperf
during the build.
In the review and test, Linus noticed gperf-3.1 had changed the lookup
function prototype. Then, the use of gperf in kernel was entirely
removed by commit bb3290d91695 ("Remove gperf usage from toolchain").
This time, I tested several versions of flex and bison, and I was not
hit by any compatibility issue except a flaw in flex-2.6.3; if you
generate lexer for dtc and genksyms with flex-2.6.3, you will see
"yywrap redefined" warning. This was not intentional, but a bug,
fixed by flex-2.6.4. Otherwise, both flex and bison look fairly
stable for a long time.
This commit prepares some build rules to remove the _shipped files.
Also, document minimal requirement for flex and bison.
Rationale for the minimal version:
The -Wmissing-prototypes option of GCC warns "no previous prototype"
for lexers generated by flex-2.5.34 or older, so I chose 2.5.35 as the
required version for flex. Flex-2.5.35 was released in 2008. Bison
looks more stable. I did not see any problem with bison-2.0, released
in 2004. I did not test bison-1.x, but bison-2.0 should be old enough.
Tested flex versions:
2.5.35
2.5.36
2.5.37
2.5.39
2.6.0
2.6.1
2.6.2
2.6.3 (*)
2.6.4
(*) flex-2.6.3 causes "yywrap redefined" warning
Tested bison versions:
2.0
2.1
2.2
2.3
2.4
2.4.1
2.5.1
2.6
2.6.1
2.6.2
2.6.3
2.6.4
2.6.5
2.7
2.7.1
3.0
3.0.1
3.0.2
3.0.3
3.0.4
Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
2017-12-09 16:02:29 +00:00
|
|
|
Flex
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
- <https://github.com/westes/flex/releases>
|
|
|
|
|
|
|
|
|
|
Bison
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
|
|
- <ftp://ftp.gnu.org/gnu/bison/>
|
|
|
|
|
|
2015-08-27 10:13:36 +00:00
|
|
|
OpenSSL
|
|
|
|
|
-------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <https://www.openssl.org/>
|
2015-08-27 10:13:36 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
System utilities
|
|
|
|
|
****************
|
|
|
|
|
|
|
|
|
|
Util-linux
|
|
|
|
|
----------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2017-03-27 13:05:34 +00:00
|
|
|
- <https://www.kernel.org/pub/linux/utils/util-linux/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2018-07-02 02:46:06 +00:00
|
|
|
Kmod
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
- <https://www.kernel.org/pub/linux/utils/kernel/kmod/>
|
|
|
|
|
- <https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git>
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Ksymoops
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2017-03-27 13:05:34 +00:00
|
|
|
- <https://www.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Mkinitrd
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <https://code.launchpad.net/initrd-tools/main>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
E2fsprogs
|
|
|
|
|
---------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-01-29 23:15:15 +00:00
|
|
|
- <https://www.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/>
|
|
|
|
|
- <https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
JFSutils
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <http://jfs.sourceforge.net/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Reiserfsprogs
|
|
|
|
|
-------------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-01-29 23:15:15 +00:00
|
|
|
- <https://git.kernel.org/pub/scm/linux/kernel/git/jeffm/reiserfsprogs.git/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Xfsprogs
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-01-29 23:15:15 +00:00
|
|
|
- <https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git>
|
|
|
|
|
- <https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-06-27 23:28:45 +00:00
|
|
|
Pcmciautils
|
|
|
|
|
-----------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2017-03-27 13:05:34 +00:00
|
|
|
- <https://www.kernel.org/pub/linux/utils/kernel/pcmcia/>
|
2005-06-27 23:28:45 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Quota-tools
|
2016-09-19 11:07:42 +00:00
|
|
|
-----------
|
|
|
|
|
|
|
|
|
|
- <http://sourceforge.net/projects/linuxquota/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-05-01 15:59:27 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Intel P6 microcode
|
|
|
|
|
------------------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <https://downloadcenter.intel.com/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
udev
|
|
|
|
|
----
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-06-21 13:36:30 +00:00
|
|
|
- <https://www.freedesktop.org/software/systemd/man/udev.html>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2005-09-28 04:45:20 +00:00
|
|
|
FUSE
|
|
|
|
|
----
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2018-03-27 12:59:50 +00:00
|
|
|
- <https://github.com/libfuse/libfuse/releases>
|
2005-09-28 04:45:20 +00:00
|
|
|
|
2009-04-28 21:37:02 +00:00
|
|
|
mcelog
|
|
|
|
|
------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <http://www.mcelog.org/>
|
2009-04-28 21:37:02 +00:00
|
|
|
|
2022-04-19 14:48:15 +00:00
|
|
|
cpio
|
|
|
|
|
----
|
|
|
|
|
|
|
|
|
|
- <https://www.gnu.org/software/cpio/>
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
Networking
|
|
|
|
|
**********
|
|
|
|
|
|
|
|
|
|
PPP
|
|
|
|
|
---
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-01-29 23:15:15 +00:00
|
|
|
- <https://download.samba.org/pub/ppp/>
|
|
|
|
|
- <https://git.ozlabs.org/?p=ppp.git>
|
|
|
|
|
- <https://github.com/paulusmack/ppp/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
NFS-utils
|
|
|
|
|
---------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <http://sourceforge.net/project/showfiles.php?group_id=14>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Iptables
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
2020-01-29 23:15:15 +00:00
|
|
|
- <https://netfilter.org/projects/iptables/index.html>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Ip-route2
|
|
|
|
|
---------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <https://www.kernel.org/pub/linux/utils/net/iproute2/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
OProfile
|
|
|
|
|
--------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <http://oprofile.sf.net/download/>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
NFS-Utils
|
|
|
|
|
---------
|
2016-09-19 11:07:42 +00:00
|
|
|
|
|
|
|
|
- <http://nfs.sourceforge.net/>
|
2016-09-19 11:07:43 +00:00
|
|
|
|
|
|
|
|
Kernel documentation
|
|
|
|
|
********************
|
|
|
|
|
|
|
|
|
|
Sphinx
|
|
|
|
|
------
|
|
|
|
|
|
2020-06-21 13:36:30 +00:00
|
|
|
- <https://www.sphinx-doc.org/>
|