From: Colin Baxter <m43cap@yandex.com>
To: Philipp <p.stephani2@gmail.com>
Cc: , Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Build failure: 'seccomp-filter'
Date: Sun, 11 Apr 2021 16:18:56 +0100 [thread overview]
Message-ID: <87a6q47stb.fsf@yandex.com> (raw)
In-Reply-To: <87C5F4EB-28C7-467C-A6CB-80D6AE861ABA@gmail.com> (Philipp's message of "Sun, 11 Apr 2021 16:31:23 +0200")
>>>>> Philipp <p.stephani2@gmail.com> writes:
>> Am 11.04.2021 um 12:45 schrieb Colin Baxter <m43cap@yandex.com>:
>>
>>>>>>> Philipp Stephani <p.stephani2@gmail.com> writes:
>>
>>> Am So., 11. Apr. 2021 um 09:51 Uhr schrieb Colin Baxter
>>> <m43cap@yandex.com>:
>>>>
>>>>>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>
>>>>> From: Colin Baxter <m43cap@yandex.com> Cc: Date: Sun, 11 Apr 2021
>>>> >> 07:45:19 +0100
>>>>>
>>>>> I get a build with the latest pull of emacs:
>>>>>
>>>>> Makefile:415: recipe for target 'seccomp-filter' failed make[1]:
>>>> >> *** [seccomp-filter] Error 1 make[1]: Leaving directory >>
>>>> '/home/redknight/git/emacs/lib-src' Makefile:396: recipe for >>
>>>> target 'lib-src' failed make: *** [lib-src] Error 2
>>>>
>>>>> Are there no error or warning messages before the
>>>> "Makefile:415" > one? If there are, please show all the
>>>> messages.
>>>>
>>>> Yes, sorry, I missed the earlier errors. Here is the full list
>>>> beginning after the attempt to compile seccomp-filter:
>>>>
>>>> ---------- Begin error list ------------
>>>>
>>>> CCLD seccomp-filter seccomp-filter.c: In function ‘main’:
>>>> seccomp-filter.c:142:23: error: ‘SCMP_ACT_KILL_PROCESS’
>>>> undeclared (first use in this function) ctx = seccomp_init
>>>> (SCMP_ACT_KILL_PROCESS); ^~~~~~~~~~~~~~~~~~~~~
>>
>>
>>> This is an interesting failure. Looks like seccomp.h exists on
>>> your system, but doesn't contain the right definitions? What
>>> does your config.log say about seccomp.h (not linux/seccomp.h)
>>> and seccomp_init?
>>
>> I have appended below the occurrences in config.log for
>> seccomp.h. (Do you want me to attach the whole config.log in a
>> second email?) The only other mentions are multiple lines of the
>> form
>>
>> 5090:| #define HAVE_LINUX_SECCOMP_H 1
>>
>> ending with
>>
>> 27758:ac_cv_header_linux_seccomp_h=yes
>> 27771:ac_cv_header_seccomp_h=yes 29332:#define
>> HAVE_LINUX_SECCOMP_H 1
>>
>> Hope this helps.
>>
>> ---------- Begin relevant portion of config.log -----------
>>
>> configure:17719: checking linux/seccomp.h usability
>> configure:17719: gcc -c -g3 -O2 -pthread -isystem
>> /usr/include/librsvg-2.0 -isystem /usr/include/gdk-pixbuf-2.0
>> -isystem /usr/include/libpng16 -isystem /usr/include/cairo
>> -isystem /usr/include/glib-2.0 -isystem
>> /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 -isystem /usr/include/cairo -isystem
>> /usr/include/glib-2.0 -isystem
>> /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 conftest.c >&5 configure:17719: $? = 0
>> configure:17719: result: yes configure:17719: checking
>> linux/seccomp.h presence configure:17719: gcc -E conftest.c
>> configure:17719: $? = 0 configure:17719: result: yes
>> configure:17719: checking for linux/seccomp.h configure:17719:
>> result: yes configure:17731: checking seccomp.h usability
>> configure:17731: gcc -c -g3 -O2 -pthread -isystem
>> /usr/include/librsvg-2.0 -isystem /usr/include/gdk-pixbuf-2.0
>> -isystem /usr/include/libpng16 -isystem /usr/include/cairo
>> -isystem /usr/include/glib-2.0 -isystem
>> /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 -isystem /usr/include/cairo -isystem
>> /usr/include/glib-2.0 -isystem
>> /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 conftest.c >&5 configure:17731: $? = 0
>> configure:17731: result: yes configure:17731: checking seccomp.h
>> presence configure:17731: gcc -E conftest.c configure:17731: $? =
>> 0 configure:17731: result: yes configure:17731: checking for
>> seccomp.h configure:17731: result: yes configure:17733: checking
>> for seccomp_init in -lseccomp configure:17758: gcc -o conftest
>> -g3 -O2 -pthread -isystem /usr/include/librsvg-2.0 -isystem
>> /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/libpng16
>> -isystem /usr/include/cairo -isystem /usr/include/glib-2.0
>> -isystem /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 -isystem /usr/include/cairo -isystem
>> /usr/include/glib-2.0 -isystem
>> /usr/lib/i386-linux-gnu/glib-2.0/include -isystem
>> /usr/include/pixman-1 -isystem /usr/include/freetype2 -isystem
>> /usr/include/libpng16 conftest.c -lseccomp -lX11 -lcairo >&5
>> configure:17758: $? = 0 configure:17767: result: yes
>>
>> ---------- End relevant portion of config.log ----
>>
>>
> OK, looks like libseccomp is available and should be working.
> Does /usr/include/seccomp.h contain at least some of the symbols
> the compiler complains about?
Well my /usr/include/seccomp.h does contain SCMP_ACT_KILL,
SCMP_CMP_MASKED_EQ, SCMP_ACT_ALLOW, but I don't understand the contents
of the file.
Best wishes, Colin.
prev parent reply other threads:[~2021-04-11 15:18 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
2021-04-12 7:22 ` Philipp Stephani
2021-04-11 15:18 ` Colin Baxter [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=87a6q47stb.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.