All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Ian Rogers <irogers@google.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-next@vger.kernel.org
Subject: Re: [PATCH] perf tools: Fix build failures on ppc64le
Date: Sun, 13 Oct 2024 20:29:44 +1100	[thread overview]
Message-ID: <20241013202925.69aa2314@oak> (raw)
In-Reply-To: <CAP-5=fWm86UcwX+B_XjFSLFJF54QP2trYzJgJF0927h-AzSV_Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

Hi Ian,

On Fri, 11 Oct 2024 00:05:21 -0700 Ian Rogers <irogers@google.com> wrote:
>
> Elsewhere for PPC we carry:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/perf/tests/bp_account.c#n3
> ```
> /*
>  * Powerpc needs __SANE_USERSPACE_TYPES__ before <linux/types.h> to select
>  * 'int-ll64.h' and avoid compile warnings when printing __u64 with %llu.
>  */
> #define __SANE_USERSPACE_TYPES__
> ```
> Given the comment I suspect we need to do similar to fix this.
> Stephen, could you test?

I added that to the start of tools/perf/util/evsel.c and it builds fine.

Thanks
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2024-10-13  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-10 23:23 linux-next: build failure after merge of the perf tree Stephen Rothwell
2024-10-10 23:57 ` [PATCH] perf tools: Fix build failures on ppc64le Namhyung Kim
2024-10-11  0:48   ` Stephen Rothwell
2024-10-11  6:34     ` Namhyung Kim
2024-10-11  7:05       ` Ian Rogers
2024-10-13  9:29         ` Stephen Rothwell [this message]

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=20241013202925.69aa2314@oak \
    --to=sfr@canb.auug.org.au \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=namhyung@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.