From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] linux-tools/perf: Add dependency on 32-bit atomics
Date: Sat, 20 Apr 2019 15:50:05 +0200 [thread overview]
Message-ID: <20190420155005.3763b1ab@windsurf> (raw)
In-Reply-To: <20190418173845.14495-1-abrodkin@synopsys.com>
Hello,
On Thu, 18 Apr 2019 20:38:45 +0300
Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> Atomic ops are strictly required by perf utility as it uses
> atomic_xxx() functions.
>
> Otherwise building fails like that:
> |.../output/host/opt/ext-toolchain/bin/../lib/gcc/arc-snps-linux-uclibc/8.2.1/../../../../arc-snps-linux-uclibc/bin/ld:
> |.../output/build/linux-5.0.7/tools/perf/libperf.a(libperf-in.o): in function `atomic_cmpxchg':
> |.../output/build/linux-5.0.7/tools/include/asm-generic/atomic-gcc.h:69: undefined reference to `__sync_val_compare_and_swap_4'
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
I have applied to master, after doing one change, see below.
> +comment "perf needs 32-bit atomic ops"
> + depends on !BR2_TOOLCHAIN_HAS_SYNC_4
> +
We typically don't add such comments, because it's an architecture
dependency. There is nothing the user can do about it, so there's no
point in having a comment.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-20 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 17:38 [Buildroot] [PATCH v2] linux-tools/perf: Add dependency on 32-bit atomics Alexey Brodkin
2019-04-20 13:50 ` Thomas Petazzoni [this message]
2019-04-24 15:30 ` Peter Korsgaard
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=20190420155005.3763b1ab@windsurf \
--to=thomas.petazzoni@bootlin.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