[PATCH staging-next] gnu: qtbase: Restore compatibility with old kernels.

  • Done
  • quality assurance status badge
Details
One participant
  • Marius Bakke
Owner
unassigned
Submitted by
Marius Bakke
Severity
normal
M
M
Marius Bakke wrote on 14 Nov 2019 17:15
(address . guix-patches@gnu.org)
20191114161526.11685-1-mbakke@fastmail.com
* gnu/packages/qt.scm (qtbase)[arguments]: Add 'no-feature-renameat2' to the
configure flags.
---
gnu/packages/qt.scm | 1 +
1 file changed, 1 insertion(+)

Toggle diff (14 lines)
diff --git a/gnu/packages/qt.scm b/gnu/packages/qt.scm
index 222a0cc867..9eb8d7e0f9 100644
--- a/gnu/packages/qt.scm
+++ b/gnu/packages/qt.scm
@@ -652,6 +652,7 @@ system, and the core design of Django is reused in Grantlee.")
;; kernels that the glibc supports, including the RHEL6
;; (2.6.32) and RHEL7 (3.10) kernels.
"-no-feature-getentropy" ; requires Linux 3.17
+ "-no-feature-renameat2" ; requires Linux 3.16
;; Do not build examples; if desired, these could go
;; into a separate output, but for the time being, we
--
2.23.0
M
M
Marius Bakke wrote on 28 Nov 2019 00:21
(address . 38210-done@debbugs.gnu.org)
87lfs07vng.fsf@devup.no
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (3 lines)
> * gnu/packages/qt.scm (qtbase)[arguments]: Add 'no-feature-renameat2' to the
> configure flags.

Pushed in f0de36cba7f9f8a6de3a579034e10516195b97e9.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl3fBQMACgkQoqBt8qM6
VPoYxAf9EgZY7/6jUDbN5+JCfM83ifnmo5ROhDRCTrzoFN7MF/GbDjziQquOWV8N
ImnGNdaS3zC7pnnYpm6sKZg+hQJHZU6h/ZU08cnWsZjZOCuc7zx8SfhMkPrvs9Pc
s2VIsi4CcIDG4FNW6Gvip4RT9SSLykJvHIVTzSjiXcrU0QGwBgDBAMhcS6ZsQmD6
yPHiMOZf2aZXmD7QcV6mHffm2AfepNxxKfFAL3YfN8HWZANZCAK152trbPDxfBKu
F+bYH4qRCYwS/yf5If5rJV1hI9qUASCZFysEgBekvU6U1AR1o1STiZW05X4TxXVV
NNdPjyglm9nidTPTuas9+ul7GPJ9fg==
=mUdk
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 38210@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 38210
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch