gitolite/buildrootschalter
gitolite/buildrootschalter
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
13d7c78394
buildrootschalter/package/oprofile/Config.in

34 lines
1.2 KiB
Plaintext
Raw Normal View History

add oprofile
2008-04-24 18:54:29 +02:00
config BR2_PACKAGE_OPROFILE
bool "oprofile"
oprofile: needs mmu Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-09 23:30:42 +02:00
depends on BR2_USE_MMU # fork()
add oprofile
2008-04-24 18:54:29 +02:00
select BR2_PACKAGE_POPT
oprofile: use new libbfd option Convert the oprofile target to select the new libbfd staging/target option to avoid a huge target binutils for a simple task. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2010-12-31 12:39:04 +01:00
select BR2_PACKAGE_BINUTILS
oprofile 0.9.8: fix compilation on powerpc The oprofile build was broken on powerpc since version 0.9.8. This was detected in several autobuilds, like http://autobuild.buildroot.net/results/6f6c02d18495907d50fcdfc6003ac20d493c55fe/ Thomas Petazzoni had some fixes pending in his own tree, and this patch is partially based on this work (credits to him). Here is an overview: - I took over (and fixed) the oprofile.mk changes, except for the powerpc- specific part. For powerpc, there is a new dependency to libpfm4. - I reimported those Yocto patches that were specific to the ppc build issues, but left out the other ones. Those can be added in separate commits. [Peter: simplify libpfm4 check] Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-03-21 10:03:17 +01:00
select BR2_PACKAGE_LIBPFM4 if BR2_powerpc
package/: depend on toolchain C++ config, don't use select select should only be used for package (library) dependencies.
2009-01-26 20:19:10 +01:00
depends on BR2_INSTALL_LIBSTDCPP
binutils: do not allow on NIOS2, no support available binutils does not have support for NIOS2 on the target, so disable the selection of binutils on this architecture. Fixes: http://autobuild.buildroot.org/results/40d/40d9cbefd03727af82610412ed0bc47674c44dbb/build-end.log Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
2013-12-22 19:31:28 +01:00
depends on !BR2_aarch64 && !BR2_nios2 # binutils
libpfm4: needs thread support 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>
2013-12-03 20:27:18 +01:00
# libpfm4 is needed on PowerPC, and requires thread support
depends on BR2_TOOLCHAIN_HAS_THREADS || !BR2_powerpc
add oprofile
2008-04-24 18:54:29 +02:00
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
buildroot: remove trailing spaces for i in `find -name 'Config*' -o -name 'Makefile*' -o -name '*.mk'`; do sed -i 's/ \+$//' $i; done
2008-08-04 21:07:05 +02:00
libraries, and applications.
package/: depend on toolchain C++ config, don't use select select should only be used for package (library) dependencies.
2009-01-26 20:19:10 +01:00
Config.in files: unify comments of toolchain option dependencies This patch lines up the comments in Config.in files that clarify which toolchain options the package depends on. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-10-13 16:55:32 +02:00
comment "oprofile needs a toolchain w/ C++"
Config.in files: add missing dependencies to toolchain option comments When a package A depends on config option B and toolchain option C, then the comment that is given when C is not fulfilled should also depend on B. For example: config BR2_PACKAGE_A depends on BR2_B depends on BR2_LARGEFILE depends on BR2_WCHAR comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR This comment should actually be: comment "A needs a toolchain w/ largefile, wchar" depends on BR2_B depends on !BR2_LARGEFILE || !BR2_WCHAR or if possible (typically when B is a package config option declared in that same Config.in file): if BR2_B comment "A needs a toolchain w/ largefile, wchar" depends on !BR2_LARGEFILE || !BR2_WCHAR [other config options depending on B] endif Otherwise, the comment would be visible even though the other dependencies are not met. This patch adds such missing dependencies, and changes existing such dependencies from depends on BR2_BASE_DEP && !BR2_TOOLCHAIN_USES_GLIBC to depends on BR2_BASE_DEP depends on !BR2_TOOLCHAIN_USES_GLIBC so that (positive) base dependencies are separate from the (negative) toolchain dependencies. This strategy makes it easier to write such comments (because one can simply copy the base dependency from the actual package config option), but also avoids complex and long boolean expressions. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> (untested) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-11-07 09:24:37 +01:00
depends on BR2_USE_MMU && !BR2_aarch64
package/: depend on toolchain C++ config, don't use select select should only be used for package (library) dependencies.
2009-01-26 20:19:10 +01:00
depends on !BR2_INSTALL_LIBSTDCPP
libpfm4: needs thread support 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>
2013-12-03 20:27:18 +01:00
comment "oprofile needs a toolchain w/ threads on PPC"
depends on BR2_USE_MMU && BR2_powerpc
depends on !BR2_TOOLCHAIN_HAS_THREADS
Reference in New Issue Copy Permalink