summaryrefslogtreecommitdiffstats
path: root/package/oprofile/Config.in
Commit message (Collapse)AuthorAgeFilesLines
* package/oprofile: introduce a BR2_PACKAGE_OPROFILE_ARCH_SUPPORTSRomain Naour2016-08-051-4/+12
| | | | | | | | | | | | | | | | | | | | operf_utils.h defines rmb() for a limited number of architectures, so add this list to BR2_PACKAGE_OPROFILE_ARCH_SUPPORTS to disable any new or unsupported architectures. Doing so, this disable oprofile for m68k which lack of memory barrier operations. Remove nios2 dependency since it's not supported by oprofile even if binutils could be built for nios2. Fixes: http://autobuild.buildroot.net/results/1cc761d8a5715d0a2c6eaacfde7e44b225da1b36 Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: remove BR2_sh64, use BR2_sh instead of BR2_sh4.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* binutils: enable as target package for aarch64Erico Nunes2016-06-081-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | binutils got disabled as a target package for aarch64 back in Buildroot 2012.11 (commit 660d16f4). The default version 2.21.1 at the time didn't really support aarch64, as shown by the autobuilder error reference in that commit. binutils has now had support for aarch64 since 2.23, but was never re-enabled for aarch64. All of the binutils versions currently supported by Buildroot (oldest being 2.24) support aarch64, so we can now enable it without any restrictions. This same patch also touches the dropwatch, lightning and oprofile packages which all select binutils and had the 'depends on !aarch64' to keep Kconfig consistent. They are now re-enabled for aarch64 as well. They are changed in this same patch so that Kconfig is kept consistent and doesn't end up having them disabled in a commit which only has the binutils change applied. lightning has other explicit arch dependencies so it is not actually yet available in aarch64, but at least the dependency on !aarch64 because of binutils is not needed anymore. Everything has been build tested with Buildroot and external toolchains. binutils and dropwatch work fine in a qemu target. oprofile doesn't seem to be supported in the qemu aarch64 processor but builds fine and seems to have some level of aarch64 support in the source, so there doesn't seem to be a reason to keep it disabled in Kconfig. Signed-off-by: Erico Nunes <nunes.erico@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* oprofile: not available on MicroblazeThomas Petazzoni2016-05-241-2/+3
| | | | | | | | | | | | | | | | | | Commit c45979c732cb610ad5d54e23dd7d4d49e519d45b marked OProfile as not available on the Xtensa architecture, due to the lack of memory barrier operations. This commit does the same for the Microblaze architecture, for the same reason, which allows to fix the following autobuilder failure: http://autobuild.buildroot.org/results/9a872ddc906e9d552d30762e849a1b537b4e5095/ It is worth mentioning that most likely Xtensa and Microblaze are architectures implementing a strongly-ordered memory model, in which case we could define the memory barriers as no-ops. But until someone who actually cares about OProfile on Xtensa and Microblaze shows up, it's probably better to disable the package on those architectures. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* oprofile: add missing indirect dependency on NPTL for PPCArnout Vandecappelle2015-02-071-3/+3
| | | | | | [Peter: also adjust comment dependencies] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* binutils: now depends on wcharAlexey Brodkin2014-10-291-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | binutils starting at least from 2.23 when build for target require uClibc configured with UCLIBC_HAS_WCHAR otherwise: libtool: link: [...] -o as-new [...] read.o: In function `read_symbol_name': read.c:(.text+0x3634): undefined reference to `mbstowcs' collect2: error: ld returned 1 exit status because "mbstowcs" is not available in the C library. Even though we're not yet using 2.23.2 as the default version, we will probably do it in the near future, so this commit doesn't bother with making the wchar dependency version-specific, and applies it to the binutils package as a whole. Fixes bug #6218 [Thomas: - more details in the commit log. - add comment about the wchar dependency - propagate the dependency to dropwatch (and fix a mistake in the architecture dependencies of the comment) - propagate the dependency to oprofile.] Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com> Cc: Anton Kolesov <akolesov@synopsys.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
* oprofile: disable on xtensaBaruch Siach2013-12-311-1/+3
| | | | | | | | | | Missing memory barrier definition. Fixes http://autobuild.buildroot.net/results/df7/df797a81111fa15de9337adefca05cbac156d0b2/. Also, add nios2 to the dependencies comment while at it. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* binutils: do not allow on NIOS2, no support availableThomas Petazzoni2013-12-251-1/+1
| | | | | | | | | | | | 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>
* libpfm4: needs thread supportThomas Petazzoni2013-12-041-0/+6
| | | | | | | | | | | | | | | 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>
* Config.in files: add missing dependencies to toolchain option commentsThomas De Schampheleire2013-11-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* Config.in files: unify comments of toolchain option dependenciesThomas De Schampheleire2013-10-141-1/+1
| | | | | | | | 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>
* oprofile: needs mmuGustavo Zacarias2013-10-091-0/+1
| | | | | Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
* oprofile 0.9.8: fix compilation on powerpcThomas De Schampheleire2013-03-241-0/+1
| | | | | | | | | | | | | | | | | | | | 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>
* binutils: not available for the target on AArch64Thomas Petazzoni2012-11-281-0/+1
| | | | | | | | | Fixes: http://autobuild.buildroot.org/results/74082860f607cbd857654e9504f5f7e7ae47c0ac/build-end.log Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* oprofile: allow builds with external toolchainsPeter Korsgaard2011-10-271-4/+0
| | | | | | | Based on patch by Benoit Mauduit. Now that we can build binutils for the target with external toolchains, oprofile is also available. Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
* oprofile: use new libbfd optionGustavo Zacarias2011-01-021-0/+1
| | | | | | | | 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>
* oprofile: disable with external toolchainThomas Petazzoni2010-07-291-0/+4
| | | | | | | | | oprofile depends on binutils_target, but binutils_target fails to build with external toolchains because the binutils version has not been choosen. As the fix is not trivial, let's just disable oprofile in external toolchain builds for the moment. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
* package/: depend on toolchain C++ config, don't use selectPeter Korsgaard2009-01-261-1/+4
| | | | select should only be used for package (library) dependencies.
* buildroot: remove trailing spacesPeter Korsgaard2008-08-041-1/+1
| | | | | | | for i in `find -name 'Config*' -o -name 'Makefile*' -o -name '*.mk'`; do sed -i 's/ \+$//' $i; done
* Kconfig: remove 'default n'Peter Korsgaard2008-07-171-1/+0
| | | | 'default n' is the default, so there's no need to say it explicitly.
* add oprofileJohn Voltz2008-04-241-0/+20
OpenPOWER on IntegriCloud