All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	linux-perf-users@vger.kernel.org, lkft-triage@lists.linaro.org
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	Tiezhu Yang <yangtiezhu@loongson.cn>,
	Namhyung Kim <namhyung@kernel.org>
Subject: next: perf: i386: bench/syscall.c:101:22: error: '__NR_execve' undeclared (first use in this function)
Date: Wed, 17 May 2023 20:34:59 +0530	[thread overview]
Message-ID: <CA+G9fYvgBR1iB0CorM8OC4AM_w_tFzyQKHc+rF6qPzJL=TbfDQ@mail.gmail.com> (raw)

Linux next perf build failing for i386 architecture.
 - build/gcc-11-lkftconfig-perf

Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>

Build log:
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/bench/syscall.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/tests/parse-events.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/util/build-id.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/util/cacheline.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/util/config.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/util/copyfile.o
  CC      /home/tuxbuild/.cache/tuxmake/builds/1/build/bench/mem-functions.o
bench/syscall.c: In function 'bench_syscall_common':
bench/syscall.c:101:22: error: '__NR_execve' undeclared (first use in
this function)
  101 |                 case __NR_execve:
      |                      ^~~~~~~~~~~
bench/syscall.c:101:22: note: each undeclared identifier is reported
only once for each function it appears in
bench/syscall.c: In function 'bench_syscall_execve':
bench/syscall.c:183:49: error: '__NR_execve' undeclared (first use in
this function)
  183 |         return bench_syscall_common(argc, argv, __NR_execve);
      |                                                 ^~~~~~~~~~~
bench/syscall.c:184:1: error: control reaches end of non-void function
[-Werror=return-type]
  184 | }
      | ^
cc1: all warnings being treated as errors

logs:
 - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230517/testrun/17031014/suite/build/test/gcc-11-lkftconfig-perf/log
 - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20230517/testrun/17031014/suite/build/test/gcc-11-lkftconfig-perf/history/


Steps to reproduce:
=============
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
#
# See https://docs.tuxmake.org/ for complete documentation.
# Original tuxmake command with fragments listed below.
# tuxmake   \
 --runtime podman   \
 --target-arch i386   \
 --toolchain gcc-11   \
 --kconfig defconfig   \
 --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/lkft.config
  \
 --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/lkft-crypto.config
  \
 --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/distro-overrides.config
  \
 --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/systemd.config
  \
 --kconfig-add https://raw.githubusercontent.com/Linaro/meta-lkft/kirkstone/meta/recipes-kernel/linux/files/virtio.config
  \
 --kconfig-add CONFIG_IGB=y   \
 --kconfig-add CONFIG_UNWINDER_FRAME_POINTER=y   \
 --kconfig-add CONFIG_SYN_COOKIES=y   \
 --kconfig-add CONFIG_FTRACE_SYSCALLS=y NO_BPF_SKEL=1 debugkernel
headers kernel modules perf


--
Linaro LKFT
https://lkft.linaro.org

             reply	other threads:[~2023-05-17 15:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 15:04 Naresh Kamboju [this message]
2023-05-18  6:47 ` next: perf: i386: bench/syscall.c:101:22: error: '__NR_execve' undeclared (first use in this function) Tiezhu Yang
2023-05-18  8:46   ` Naresh Kamboju

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='CA+G9fYvgBR1iB0CorM8OC4AM_w_tFzyQKHc+rF6qPzJL=TbfDQ@mail.gmail.com' \
    --to=naresh.kamboju@linaro.org \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=dan.carpenter@linaro.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=lkft-triage@lists.linaro.org \
    --cc=namhyung@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    /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.