From: Philipp Stephani <p.stephani2@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
53484@debbugs.gnu.org, "Mark A. Hershberger" <mah@everybody.org>
Subject: bug#53484: 29.0.50; Removing libseccomp-dev 2.5.1-1~bpo10+1 allows emacs to compile
Date: Tue, 25 Jan 2022 21:15:53 +0100 [thread overview]
Message-ID: <E92A0F34-18DE-448A-BA23-D0206414BC6D@gmail.com> (raw)
In-Reply-To: <3v4k5spzlp.fsf@fencepost.gnu.org>
> Am 24.01.2022 um 22:56 schrieb Glenn Morris <rgm@gnu.org>:
>
>
> I note that the required version of libseccomp in emacs-28 (2.5.2) is
> now greater than that found in eg rhel 8.5 (2.5.1). So there are some
> platforms where libseccomp support was working in earlier emacs-28
> pretests but is now absent.
Note that this only refers to the construction of the seccomp filter that we build for convenience. The Emacs binary itself and the actual seccomp sandboxing mechanism doesn't depend on libseccomp. Users that don't have libseccomp or an older version will still get the seccomp support, just not the specific filter file that we provide.
prev parent reply other threads:[~2022-01-25 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 20:25 bug#53484: 29.0.50; Removing libseccomp-dev 2.5.1-1~bpo10+1 allows emacs to compile Mark A. Hershberger via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-24 10:46 ` 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 [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
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=E92A0F34-18DE-448A-BA23-D0206414BC6D@gmail.com \
--to=p.stephani2@gmail.com \
--cc=53484@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mah@everybody.org \
--cc=rgm@gnu.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).