Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/oprofile: disable for m68k
Date: Thu,  4 Aug 2016 23:58:05 +0200	[thread overview]
Message-ID: <1470347885-13186-1-git-send-email-romain.naour@gmail.com> (raw)

As for Xtensa [1] and Microblaze [2], disable m68k due to the lack of
memory barrier operations.

Fixes:
http://autobuild.buildroot.net/results/1cc/1cc761d8a5715d0a2c6eaacfde7e44b225da1b36

[1] c45979c732cb610ad5d54e23dd7d4d49e519d45b
[2] b71bdd68562f82db9d5515de1ca4a33789c05cb9

Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
v2: fix the comment dependency.
---
 package/oprofile/Config.in | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/package/oprofile/Config.in b/package/oprofile/Config.in
index 9014d9f..4f491cb 100644
--- a/package/oprofile/Config.in
+++ b/package/oprofile/Config.in
@@ -8,7 +8,7 @@ config BR2_PACKAGE_OPROFILE
 	depends on !BR2_nios2 # binutils
 	depends on BR2_USE_WCHAR # binutils
 	# no memory barrier functions
-	depends on !BR2_xtensa && !BR2_microblaze
+	depends on !BR2_xtensa && !BR2_microblaze && !BR2_m68k
 	# libpfm4 is needed on PowerPC, and requires thread support
 	depends on BR2_TOOLCHAIN_HAS_THREADS_NPTL || !BR2_powerpc
 	help
@@ -29,7 +29,8 @@ config BR2_PACKAGE_OPROFILE
 
 comment "oprofile needs a toolchain w/ C++, wchar"
 	depends on BR2_USE_MMU
-	depends on !BR2_nios2 && !BR2_xtensa && !BR2_microblaze
+	depends on !BR2_nios2 && !BR2_xtensa && !BR2_microblaze && \
+		!BR2_m68k
 	depends on !BR2_INSTALL_LIBSTDCPP || !BR2_USE_WCHAR
 
 comment "oprofile needs a toolchain w/ NPTL on PPC"
-- 
2.5.5

             reply	other threads:[~2016-08-04 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 21:58 Romain Naour [this message]
2016-08-04 22:10 ` [Buildroot] [PATCH v2] package/oprofile: disable for m68k Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1470347885-13186-1-git-send-email-romain.naour@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox