09100a3750
Fixes: http://autobuild.buildroot.net/results/73d736dd3c8a70358ef4b19a63dda46178cf8bf1/ Note that the propagation of the thread dependency to the oprofile package is a little bit non standard, because oprofile selects libpfm4 only on the PowerPC architecture. So we ensure the thread dependency is only enforced on PowerPC, and a separate comment is displayed when thread support is not available, but the PowerPC architecture is used. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
config BR2_PACKAGE_OPROFILE
|
|
bool "oprofile"
|
|
depends on BR2_USE_MMU # fork()
|
|
select BR2_PACKAGE_POPT
|
|
select BR2_PACKAGE_BINUTILS
|
|
select BR2_PACKAGE_LIBPFM4 if BR2_powerpc
|
|
depends on BR2_INSTALL_LIBSTDCPP
|
|
depends on !BR2_aarch64 # binutils
|
|
# libpfm4 is needed on PowerPC, and requires thread support
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS || !BR2_powerpc
|
|
help
|
|
OProfile is a system-wide profiler for Linux systems,
|
|
capable of profiling all running code at low overhead.
|
|
OProfile is released under the GNU GPL.
|
|
|
|
It consists of a kernel driver and a daemon for collecting
|
|
sample data, and several post-profiling tools for turning
|
|
data into information.
|
|
|
|
OProfile leverages the hardware performance counters of the
|
|
CPU to enable profiling of a wide variety of interesting
|
|
statistics, which can also be used for basic time-spent
|
|
profiling. All code is profiled: hardware and software
|
|
interrupt handlers, kernel modules, the kernel, shared
|
|
libraries, and applications.
|
|
|
|
comment "oprofile needs a toolchain w/ C++"
|
|
depends on BR2_USE_MMU && !BR2_aarch64
|
|
depends on !BR2_INSTALL_LIBSTDCPP
|
|
|
|
comment "oprofile needs a toolchain w/ threads on PPC"
|
|
depends on BR2_USE_MMU && BR2_powerpc
|
|
depends on !BR2_TOOLCHAIN_HAS_THREADS
|