20b1446669
The kernel source tree also contains the sources for various userland
tools, of which cpupower, perf or selftests.
Currently, we have support for building those tools as part of the
kernel build procedure. This looked the correct thing to do so far,
because, well, they *are* part of the kernel source tree and some
really have to be the same version as the kernel that will run.
However, this is causing quite a non-trivial-to-break circular
dependency in some configurations. For example, this defconfig fails to
build (similar to the one reported by Paul):
BR2_arm=y
BR2_cortex_a7=y
BR2_ARM_FPU_NEON_VFPV4=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_INIT_SYSTEMD=y
BR2_LINUX_KERNEL=y
BR2_LINUX_KERNEL_CUSTOM_GIT=y
BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git"
BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="26f3b72a9c049be10e6af196252283e1f6ab9d1f"
BR2_LINUX_KERNEL_DEFCONFIG="bcm2709"
BR2_PACKAGE_LINUX_TOOLS_CPUPOWER=y
BR2_PACKAGE_CRYPTODEV=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_LIBCURL=y
This causes a circular dependency, as explained by Thomas:
- When libcurl is enabled, systemd depends on it
- When OpenSSL is enabled, obviously, will use it for SSL support
- When cryptodev-linux is enabled, OpenSSL will depend on it to use
crypto accelerators supported in the kernel via cryptodev-linux.
- cryptodev-linux being a kernel module, it depends on linux
- linux by itself (the kernel) does not depend on pciutils, but the
linux tool "cpupower" (managed in linux-tool-cpupower) depends on
pciutils
- pciutils depends on udev when available
- udev is provided by systemd.
And indeed, during the build, we can see that make warns (it's only
reported as a *warning*, not as an actual error):
[...]
make[1]: Circular /home/ymorin/dev/buildroot/O/build/openssl-1.0.2h/.stamp_configured
<- cryptodev-linux dependency dropped.
>>> openssl 1.0.2h Downloading
[...]
So the build fails later on, when openssl is actually built:
eng_cryptodev.c:57:31: fatal error: crypto/cryptodev.h: No such file or directory
compilation terminated.
<builtin>: recipe for target 'eng_cryptodev.o' failed
Furthermore, graph-depends also detects the circular dependency, but
treats it as a hard-error:
Recursion detected for : cryptodev-linux
which is a dependency of: openssl
which is a dependency of: libcurl
which is a dependency of: systemd
which is a dependency of: udev
which is a dependency of: pciutils
which is a dependency of: linux
which is a dependency of: cryptodev-linux
Makefile:738: recipe for target 'graph-depends' failed
Of course, there is no way to break the loop without losing
functionality in either one of the involved packages *and* keep
our infrastructure and packages as-is.
The only solution is to break the loop at the linux-tools level, by
moving them away into their own package, so that the linux package will
no longer have the opportunity to depend on another package via a
dependency of one the tools.
All three linux tools are thus moved away to their own package.
The package infrastructure only knows of three types of packages: those
in package/ , in boot/ , in toolchain/ and the one in linux/ . So we
create that new linux-tools package in package/ so that we don't have to
fiddle with yet another special case in the infra. Still, we want its
configure options to appear in the kernel's sub-menu.
So, we make it a prompt-less package, with only the tools visible as
options of that package, but without the usual dependency on their
master symbol; they only depend on the Linux kernel.
Furthermore, because the kernel is such a huge pile of code, we would
not be very happy to extract it a second time just for the sake of a few
tools. We can't extract only the tools/ sub-directory from the kernel
source either, because some tools have hard-coded path to includes from
the kernel (arch and stuff).
Instead, we just use the linux source tree as our own build tree, and
ensure the linux tree is extracted and patched before linux-tools is
configured and built.
Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Paul Ashford <paul.ashford@zurria.co.uk>
[Thomas:
- fix typo #(@D) -> $(@D)
- fix the inclusion of the per-tool .mk files.]
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
66 lines
2.1 KiB
Plaintext
66 lines
2.1 KiB
Plaintext
menu "Linux Kernel Tools"
|
|
|
|
# No prompt, this is sourced by linux/Config.in as this
|
|
# is no real package and really belongs to the kernel.
|
|
config BR2_PACKAGE_LINUX_TOOLS
|
|
bool
|
|
|
|
config BR2_PACKAGE_LINUX_TOOLS_CPUPOWER
|
|
bool "cpupower"
|
|
depends on !BR2_bfin # pciutils
|
|
depends on BR2_USE_WCHAR || !BR2_NEEDS_GETTEXT # gettext
|
|
select BR2_PACKAGE_LINUX_TOOLS
|
|
select BR2_PACKAGE_PCIUTILS
|
|
select BR2_PACKAGE_GETTEXT if BR2_NEEDS_GETTEXT
|
|
help
|
|
cpupower is a collection of tools to examine and tune power
|
|
saving related features of your processor.
|
|
|
|
comment "cpupower needs a toolchain w/ wchar"
|
|
depends on !BR2_bfin
|
|
depends on !BR2_USE_WCHAR && BR2_NEEDS_GETTEXT
|
|
|
|
config BR2_PACKAGE_LINUX_TOOLS_PERF
|
|
bool "perf"
|
|
select BR2_PACKAGE_LINUX_TOOLS
|
|
help
|
|
perf (sometimes "Perf Events" or perf tools, originally
|
|
"Performance Counters for Linux") - is a performance
|
|
analyzing tool in Linux, available from kernel version
|
|
2.6.31. User-space controlling utility, called 'perf' has
|
|
git-like interface with subcommands. It is capable of
|
|
statistical profiling of entire system (both kernel and user
|
|
code), single CPU or severals threads.
|
|
|
|
This will build and install the userspace 'perf'
|
|
command. It is up to the user to ensure that the kernel
|
|
configuration has all the suitable options enabled to allow a
|
|
proper operation of 'perf'.
|
|
|
|
https://perf.wiki.kernel.org/
|
|
|
|
config BR2_PACKAGE_LINUX_TOOLS_SELFTESTS
|
|
bool"selftests"
|
|
depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS # bash
|
|
depends on BR2_USE_MMU # bash
|
|
select BR2_PACKAGE_LINUX_TOOLS
|
|
select BR2_PACKAGE_BASH # runtime
|
|
select BR2_PACKAGE_POPT
|
|
select BR2_PACKAGE_LIBCAP_NG
|
|
help
|
|
Build and install (to /usr/lib/kselftests) kernel selftests.
|
|
|
|
Use of this option implies you know the process of using and
|
|
compiling the kernel selftests. The Makefile to build and
|
|
install these is very noisy and may appear to cause your
|
|
build to fail for strange reasons.
|
|
|
|
This is very much a use at your risk option and may not work
|
|
for every setup or every architecture.
|
|
|
|
comment "selftests needs BR2_PACKAGE_BUSYBOX_SHOW_OTHERS"
|
|
depends on BR2_USE_MMU
|
|
depends on !BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
|
|
|
|
endmenu
|