From: "Mark A. Hershberger" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 53484@debbugs.gnu.org
Subject: bug#53484: 29.0.50; Removing libseccomp-dev 2.5.1-1~bpo10+1 allows emacs to compile
Date: Sun, 23 Jan 2022 15:25:24 -0500 [thread overview]
Message-ID: <87bl02td1n.fsf@everybody.org> (raw)
I haven't compiled emacs in a while, but I decided to try it today and
it kept failing on some lines indicating a problem with seccomp.
After removing the debian package in the subject line, compilation was successful.
What am I missing without seccomp?
Some of the info from report-bug:
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0)
of 2022-01-23 built on silk
Repository revision: f4af1137e663f2644a30778a5466909cac26b4b3
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12004000
System Description: Debian GNU/Linux 10 (buster)
Configured using:
'configure --with-cairo --with-imagemagick --with-json
--with-native-compilation --with-xinput2 --with-xwidgets
--with-modules'
Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ
IMAGEMAGICK JPEG JSON LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2
M17N_FLT MODULES NATIVE_COMP NOTIFY INOTIFY PDUMPER PNG RSVG SECCOMP
SOUND SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS WEBP X11 XDBE XIM XINPUT2
XPM XWIDGETS GTK3 ZLIB
Important settings:
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: @im=ibus
locale-coding-system: utf-8-unix
next reply other threads:[~2022-01-23 20:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 20:25 Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-24 10:46 ` bug#53484: 29.0.50; Removing libseccomp-dev 2.5.1-1~bpo10+1 allows emacs to compile Philipp Stephani
2022-01-24 14:58 ` Mark A. Hershberger
2022-01-24 20:12 ` Lars Ingebrigtsen
2022-01-24 21:56 ` Glenn Morris
2022-01-25 12:05 ` Lars Ingebrigtsen
2022-01-25 20:15 ` Philipp Stephani
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=87bl02td1n.fsf@everybody.org \
--to=bug-gnu-emacs@gnu.org \
--cc=53484@debbugs.gnu.org \
--cc=mah@everybody.org \
/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).