From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Colin Baxter Newsgroups: gmane.emacs.devel Subject: Re: Build failure: 'seccomp-filter' Date: Sun, 11 Apr 2021 16:18:56 +0100 Message-ID: <87a6q47stb.fsf@yandex.com> References: <871rbhs4jk.fsf@yandex.com> <83mtu546b0.fsf@gnu.org> <87wnt9qmxz.fsf@yandex.com> <87pmz1p0ag.fsf@yandex.com> <87C5F4EB-28C7-467C-A6CB-80D6AE861ABA@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37729"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cc: , Eli Zaretskii , Emacs developers To: Philipp Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 11 17:19:57 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lVbsS-0009eL-Oh for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 17:19:56 +0200 Original-Received: from localhost ([::1]:46006 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVbsR-0003J5-Nt for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 11:19:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51418) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVbrf-0002ol-Fi for emacs-devel@gnu.org; Sun, 11 Apr 2021 11:19:07 -0400 Original-Received: from forward101p.mail.yandex.net ([77.88.28.101]:59556) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVbrc-0006iY-17; Sun, 11 Apr 2021 11:19:06 -0400 Original-Received: from forward100q.mail.yandex.net (forward100q.mail.yandex.net [IPv6:2a02:6b8:c0e:4b:0:640:4012:bb97]) by forward101p.mail.yandex.net (Yandex) with ESMTP id 0616F32801A2; Sun, 11 Apr 2021 18:18:59 +0300 (MSK) Original-Received: from vla1-5340769fcd0e.qloud-c.yandex.net (vla1-5340769fcd0e.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:d1d:0:640:5340:769f]) by forward100q.mail.yandex.net (Yandex) with ESMTP id 015E27080002; Sun, 11 Apr 2021 18:18:59 +0300 (MSK) Original-Received: from vla5-445dc1c4c112.qloud-c.yandex.net (vla5-445dc1c4c112.qloud-c.yandex.net [2a02:6b8:c18:3609:0:640:445d:c1c4]) by vla1-5340769fcd0e.qloud-c.yandex.net (mxback/Yandex) with ESMTP id BwMf9ISSZL-IwJma7o3; Sun, 11 Apr 2021 18:18:58 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1618154338; bh=R2cLFFrbG+0SCR2bt6n+E2Dc5vxNV+LbrYjOY8TCzjs=; h=In-Reply-To:Subject:To:From:Message-ID:Cc:Cc:Date:References; b=vOgjkry1MwM2fl4EoKnW/VHyHD9GfY74dHRfbp5lfy/nEudmeBoQI7tuqRnCeGOQY jq/4QcpqugNM+RPBgXGvYHAlHNvTBy2FNaKNEH5b5YBwvi0tYa8nZy/ThWLkJJ6/yh /8SVieXZlh9uYhisCDfJ34dClXf7fxrFAX7KtG94= Authentication-Results: vla1-5340769fcd0e.qloud-c.yandex.net; dkim=pass header.i=@yandex.com Original-Received: by vla5-445dc1c4c112.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id iIv9w4hLVU-IvKSU7UD; Sun, 11 Apr 2021 18:18:57 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) X-Face: BHjiJOg/Qmj'BQgsAKL@])L)e62P)C"Y=6T In-Reply-To: <87C5F4EB-28C7-467C-A6CB-80D6AE861ABA@gmail.com> (Philipp's message of "Sun, 11 Apr 2021 16:31:23 +0200") Face: iVBORw0KGgoAAAANSUhEUgAAAGQAAAAeBAMAAAAodabAAAAAB3RJTUUH1wQdAAY04/L8hgAA AAlwSFlzAAAewQAAHsEBw2lUUwAAAARnQU1BAACxjwv8YQUAAAASUExURc7OzpwAAAAAAP////8A AGNj/2aqqTQAAAA8SURBVHjaYzA2NnEBAmdj01D8wNgYpM7F2JiBgYFREAgEGJiU8AMGBpA6QaCG UVtGbRm1ZdSWUVsGjS0Aq20lJnMawnkAAAAASUVORK5CYII= Received-SPF: pass client-ip=77.88.28.101; envelope-from=m43cap@yandex.com; helo=forward101p.mail.yandex.net X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:267887 Archived-At: >>>>> Philipp writes: >> Am 11.04.2021 um 12:45 schrieb Colin Baxter : >>=20 >>>>>>> Philipp Stephani writes: >>=20 >>> Am So., 11. Apr. 2021 um 09:51 Uhr schrieb Colin Baxter >>> : >>>>=20 >>>>>>>>> Eli Zaretskii writes: >>>>=20 >>>>> From: Colin Baxter Cc: Date: Sun, 11 Apr 2021 >>>> >> 07:45:19 +0100 >>>>>=20 >>>>> I get a build with the latest pull of emacs: >>>>>=20 >>>>> 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 >>>>=20 >>>>> Are there no error or warning messages before the >>>> "Makefile:415" > one? If there are, please show all the >>>> messages. >>>>=20 >>>> Yes, sorry, I missed the earlier errors. Here is the full list >>>> beginning after the attempt to compile seccomp-filter: >>>>=20 >>>> ---------- Begin error list ------------ >>>>=20 >>>> CCLD seccomp-filter seccomp-filter.c: In function =E2=80=98main=E2= =80=99: >>>> seccomp-filter.c:142:23: error: =E2=80=98SCMP_ACT_KILL_PROCESS=E2= =80=99 >>>> undeclared (first use in this function) ctx =3D seccomp_init >>>> (SCMP_ACT_KILL_PROCESS); ^~~~~~~~~~~~~~~~~~~~~ >>=20 >>=20 >>> 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? >>=20 >> 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 >>=20 >> 5090:| #define HAVE_LINUX_SECCOMP_H 1 >>=20 >> ending with >>=20 >> 27758:ac_cv_header_linux_seccomp_h=3Dyes >> 27771:ac_cv_header_seccomp_h=3Dyes 29332:#define >> HAVE_LINUX_SECCOMP_H 1 >>=20 >> Hope this helps. >>=20 >> ---------- Begin relevant portion of config.log ----------- >>=20 >> 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: $? =3D 0 >> configure:17719: result: yes configure:17719: checking >> linux/seccomp.h presence configure:17719: gcc -E conftest.c >> configure:17719: $? =3D 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: $? =3D 0 >> configure:17731: result: yes configure:17731: checking seccomp.h >> presence configure:17731: gcc -E conftest.c configure:17731: $? =3D >> 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: $? =3D 0 configure:17767: result: yes >>=20 >> ---------- End relevant portion of config.log ---- >>=20 >>=20 > 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.