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:40:48 +0100 Message-ID: <87h7kcn81r.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="12015"; 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 Stephani Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Apr 11 17:42:07 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 1lVcDu-0002yU-D0 for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 17:42:06 +0200 Original-Received: from localhost ([::1]:57938 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lVcDt-0001LV-DQ for ged-emacs-devel@m.gmane-mx.org; Sun, 11 Apr 2021 11:42:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54676) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVcCu-0000wn-2r for emacs-devel@gnu.org; Sun, 11 Apr 2021 11:41:04 -0400 Original-Received: from forward103p.mail.yandex.net ([77.88.28.106]:57157) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lVcCo-00032v-St; Sun, 11 Apr 2021 11:41:03 -0400 Original-Received: from forward103q.mail.yandex.net (forward103q.mail.yandex.net [IPv6:2a02:6b8:c0e:50:0:640:b21c:d009]) by forward103p.mail.yandex.net (Yandex) with ESMTP id 81BE818C16F6; Sun, 11 Apr 2021 18:40:51 +0300 (MSK) Original-Received: from vla1-25221a47e1d2.qloud-c.yandex.net (vla1-25221a47e1d2.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:3c06:0:640:2522:1a47]) by forward103q.mail.yandex.net (Yandex) with ESMTP id 7F39861E0017; Sun, 11 Apr 2021 18:40:51 +0300 (MSK) Original-Received: from vla5-47b3f4751bc4.qloud-c.yandex.net (vla5-47b3f4751bc4.qloud-c.yandex.net [2a02:6b8:c18:3508:0:640:47b3:f475]) by vla1-25221a47e1d2.qloud-c.yandex.net (mxback/Yandex) with ESMTP id UoQ64OTFGO-epJeiuLL; Sun, 11 Apr 2021 18:40:51 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1618155651; bh=7UOOP4AB36iecWlL+2GZFr5XfZQ+QeCCrQrWalj/JS0=; h=In-Reply-To:Subject:To:From:Message-ID:Cc:Cc:Date:References; b=Zognm7jjViJKsMEXHTaJ+o4TGrO5UunUV/PNhuA3hbumR0+NXXwSGp1FrMvKElsqC eNyKWSZ3M5MGRgUXXfPEt2JSECUWjBxDI2P5kETApNmVHwKJoQVy8NgtTCrm/VHL8B bYgDYeAhcL30jeT4ZHvM/8YI9n99xP2bRy6QorC4= Authentication-Results: vla1-25221a47e1d2.qloud-c.yandex.net; dkim=pass header.i=@yandex.com Original-Received: by vla5-47b3f4751bc4.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id 2L1oy1QPa8-eoKaGuHO; Sun, 11 Apr 2021 18:40:50 +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: (Philipp Stephani's message of "Sun, 11 Apr 2021 16:52:16 +0200") Face: iVBORw0KGgoAAAANSUhEUgAAAGQAAAAeBAMAAAAodabAAAAAB3RJTUUH1wQdAAY04/L8hgAA AAlwSFlzAAAewQAAHsEBw2lUUwAAAARnQU1BAACxjwv8YQUAAAASUExURc7OzpwAAAAAAP////8A AGNj/2aqqTQAAAA8SURBVHjaYzA2NnEBAmdj01D8wNgYpM7F2JiBgYFREAgEGJiU8AMGBpA6QaCG UVtGbRm1ZdSWUVsGjS0Aq20lJnMawnkAAAAASUVORK5CYII= Received-SPF: pass client-ip=77.88.28.106; envelope-from=m43cap@yandex.com; helo=forward103p.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_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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:267890 Archived-At: >>>>> Philipp Stephani writes: > Am So., 11. Apr. 2021 um 16:40 Uhr schrieb Philipp Stephani > : >>=20 >> Am So., 11. Apr. 2021 um 16:31 Uhr schrieb Philipp >> : >> > >> > >> > >> > > Am 11.04.2021 um 12:45 schrieb Colin Baxter >> : >> > > >> > >>>>>> Philipp Stephani writes: >> > > >> > >> Am So., 11. Apr. 2021 um 09:51 Uhr schrieb Colin Baxter > >> >> : >> > >>> >> > >>>>>>>> Eli Zaretskii writes: >> > >>> >> > >>>>> From: Colin Baxter 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 =E2=80=98mai= n=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); ^~~~~~~~~~~~~~~~~~~~~ >> > > >> > > >> > >> 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=3Dyes > > >> 27771:ac_cv_header_seccomp_h=3Dyes > > 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: $? =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 >> > > >> > > ---------- 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? >> > >>=20 >> Looking at >> https://github.com/seccomp/libseccomp/blob/main/CHANGELOG, I >> guess we need at least version 2.4.0 of libseccomp. I'll see that >> I can add a few more checks to configure.ac. > With commit 725fc96b706c57ef8ceca5e7d82b175d9a72e845, I've now > switched to using pkg-config, which seems cleaner anyway. This seems to be successful. With commit 725fc96b70, I can now build emacs-28.0.50. Thanks you. Best wishes, Colin Baxter.