emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs-28 6d3608be88: Seccomp: improve support for newer versions of


From: Eli Zaretskii
Subject: Re: emacs-28 6d3608be88: Seccomp: improve support for newer versions of glibc (Bug#51073)
Date: Mon, 24 Jan 2022 14:53:42 +0200

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 24 Jan 2022 11:44:34 +0100
> Cc: Philipp Stephani <phst@google.com>, Emacs developers <emacs-devel@gnu.org>
> 
> Am Mo., 24. Jan. 2022 um 01:09 Uhr schrieb Po Lu <luangruo@yahoo.com>:
> >
> > Philipp Stephani <p.stephani2@gmail.com> writes:
> >
> > > branch: emacs-28
> > > commit 6d3608be88e1b30d2d10ee81f14dd485275c20ff
> > > Author: Philipp Stephani <phst@google.com>
> > > Commit: Philipp Stephani <phst@google.com>
> > >
> > >     Seccomp: improve support for newer versions of glibc (Bug#51073)
> > >
> > >     * lib-src/seccomp-filter.c (main): Allow 'pread64' and 'faccessat2'
> > >     system calls.  Newer versions of glibc use these system call (starting
> > >     with commits 95c1056962a3f2297c94ce47f0eaf0c5b6563231 and
> > >     3d3ab573a5f3071992cbc4f57d50d1d29d55bde2, respectively).
> >
> > This seems to break the build for many people running older glibc
> > versions.
> 
> I forgot to bump the minimum libseccomp version. I've done that now
> (commit c34d06e3d75bfbea2605e3ae292850175ce5c235).

Why do we need this and the previous change on the release branch?
There were zero complaints until now about seccomp for Emacs 28.  Can
we revert the original change in the first place?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]