unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Colin Baxter <m43cap@yandex.com>, Eli Zaretskii <eliz@gnu.org>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: Build failure: 'seccomp-filter'
Date: Mon, 12 Apr 2021 00:31:48 +0200	[thread overview]
Message-ID: <87h7kc8ncb.fsf@igel.home> (raw)
In-Reply-To: <CAArVCkQuxmYUcbC_J=OtuPTVfjv+sbC_qOs6i22K9s6p2O+ojw@mail.gmail.com> (Philipp Stephani's message of "Sun, 11 Apr 2021 20:50:41 +0200")

There are now different failures:

<https://build.opensuse.org/package/live_build_log/home:AndreasSchwab:emacs:master/emacs/15.2/x86_64>

seccomp-filter.c: In function ‘main’:
seccomp-filter.c:356:34: error: ‘SECCOMP_SET_MODE_FILTER’ undeclared (first use in this function); did you mean ‘HAVE_DECL_SECCOMP_SET_MODE_FILTER’?
         SCMP_A0_32 (SCMP_CMP_EQ, SECCOMP_SET_MODE_FILTER),
                                  ^
seccomp-filter.c:112:48: note: in definition of macro ‘RULE’
       const struct scmp_arg_cmp arg_array[] = {__VA_ARGS__};         \
                                                ^~~~~~~~~~~
/usr/include/libseccomp/seccomp.h:211:2: note: in expansion of macro ‘SCMP_CMP64’
  SCMP_CMP64(x, y, (uint32_t)(z))
  ^~~~~~~~~~
/usr/include/libseccomp/seccomp.h:209:2: note: in expansion of macro ‘_SCMP_CMP32_1’
  func ## nargs
  ^~~~
/usr/include/libseccomp/seccomp.h:244:28: note: in expansion of macro ‘SCMP_CMP32’
 #define SCMP_A0_32(x, ...) SCMP_CMP32(0, x, __VA_ARGS__)
                            ^~~~~~~~~~
seccomp-filter.c:356:9: note: in expansion of macro ‘SCMP_A0_32’
         SCMP_A0_32 (SCMP_CMP_EQ, SECCOMP_SET_MODE_FILTER),
         ^~~~~~~~~~
seccomp-filter.c:356:34: note: each undeclared identifier is reported only once for each function it appears in
         SCMP_A0_32 (SCMP_CMP_EQ, SECCOMP_SET_MODE_FILTER),
                                  ^
seccomp-filter.c:112:48: note: in definition of macro ‘RULE’
       const struct scmp_arg_cmp arg_array[] = {__VA_ARGS__};         \
                                                ^~~~~~~~~~~
/usr/include/libseccomp/seccomp.h:211:2: note: in expansion of macro ‘SCMP_CMP64’
  SCMP_CMP64(x, y, (uint32_t)(z))
  ^~~~~~~~~~
/usr/include/libseccomp/seccomp.h:209:2: note: in expansion of macro ‘_SCMP_CMP32_1’
  func ## nargs
  ^~~~
/usr/include/libseccomp/seccomp.h:244:28: note: in expansion of macro ‘SCMP_CMP32’
 #define SCMP_A0_32(x, ...) SCMP_CMP32(0, x, __VA_ARGS__)
                            ^~~~~~~~~~
seccomp-filter.c:356:9: note: in expansion of macro ‘SCMP_A0_32’
         SCMP_A0_32 (SCMP_CMP_EQ, SECCOMP_SET_MODE_FILTER),
         ^~~~~~~~~~
seccomp-filter.c:357:34: error: ‘SECCOMP_FILTER_FLAG_TSYNC’ undeclared (first use in this function); did you mean ‘SCMP_FLTATR_CTL_TSYNC’?
         SCMP_A1_32 (SCMP_CMP_EQ, SECCOMP_FILTER_FLAG_TSYNC));
                                  ^
seccomp-filter.c:112:48: note: in definition of macro ‘RULE’
       const struct scmp_arg_cmp arg_array[] = {__VA_ARGS__};         \
                                                ^~~~~~~~~~~
/usr/include/libseccomp/seccomp.h:211:2: note: in expansion of macro ‘SCMP_CMP64’
  SCMP_CMP64(x, y, (uint32_t)(z))
  ^~~~~~~~~~
/usr/include/libseccomp/seccomp.h:209:2: note: in expansion of macro ‘_SCMP_CMP32_1’
  func ## nargs
  ^~~~
/usr/include/libseccomp/seccomp.h:255:28: note: in expansion of macro ‘SCMP_CMP32’
 #define SCMP_A1_32(x, ...) SCMP_CMP32(1, x, __VA_ARGS__)
                            ^~~~~~~~~~
seccomp-filter.c:357:9: note: in expansion of macro ‘SCMP_A1_32’
         SCMP_A1_32 (SCMP_CMP_EQ, SECCOMP_FILTER_FLAG_TSYNC));
         ^~~~~~~~~~


Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."



  reply	other threads:[~2021-04-11 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-11  6:45 Build failure: 'seccomp-filter' Colin Baxter
2021-04-11  7:41 ` Eli Zaretskii
2021-04-11  7:50   ` Colin Baxter
2021-04-11 10:12     ` Philipp Stephani
2021-04-11 10:45       ` Colin Baxter
2021-04-11 14:31         ` Philipp
2021-04-11 14:40           ` Philipp Stephani
2021-04-11 14:52             ` Philipp Stephani
2021-04-11 15:40               ` Colin Baxter
2021-04-11 15:55               ` Andreas Schwab
2021-04-11 17:03                 ` Colin Baxter
2021-04-11 18:50                 ` Philipp Stephani
2021-04-11 22:31                   ` Andreas Schwab [this message]
2021-04-12  7:22                     ` Philipp Stephani
2021-04-11 15:18           ` Colin Baxter

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87h7kc8ncb.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=m43cap@yandex.com \
    --cc=p.stephani2@gmail.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).