From: "David Seifert" <soap@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-misc/boinc/
Date: Sat, 7 May 2016 22:32:45 +0000 (UTC) [thread overview]
Message-ID: <1462660308.87fb055e1198f9f343c3f2991154f323d7187e60.soap@gentoo> (raw)
commit: 87fb055e1198f9f343c3f2991154f323d7187e60
Author: Sven Eden <yamakuzure <AT> gmx <DOT> net>
AuthorDate: Fri May 6 15:40:09 2016 +0000
Commit: David Seifert <soap <AT> gentoo <DOT> org>
CommitDate: Sat May 7 22:31:48 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=87fb055e
sci-misc/boinc: Fix VSYSCALL check for boinc-7.2.42
Gentoo-Bug: 578750
The configuration options were misunderstood.
- CONFIG_X86_VSYSCALL_EMULATION only enables a dmesg message if any
legacy application tries to use any vsyscall. If disabled, these
applications simply segfault with no output in dmesg.
- To make the old calls available, either
CONFIG_LEGACY_VSYSCALL_NATIVE or CONFIG_LEGACY_VSYSCALL_EMULATE
must be used.
Therefore the ebuild was reverted to check against the
CONFIG_LEGACY_VSYSCALL_NONE option, and warns the user if this is
set.
Package-Manager: portage-2.2.28
...inc-7.2.42-r1.ebuild => boinc-7.2.42-r2.ebuild} | 34 +++++++++-------------
1 file changed, 13 insertions(+), 21 deletions(-)
diff --git a/sci-misc/boinc/boinc-7.2.42-r1.ebuild b/sci-misc/boinc/boinc-7.2.42-r2.ebuild
similarity index 78%
rename from sci-misc/boinc/boinc-7.2.42-r1.ebuild
rename to sci-misc/boinc/boinc-7.2.42-r2.ebuild
index ae58b2d..a7c9d06 100644
--- a/sci-misc/boinc/boinc-7.2.42-r1.ebuild
+++ b/sci-misc/boinc/boinc-7.2.42-r2.ebuild
@@ -50,32 +50,24 @@ DEPEND="${RDEPEND}
S="${WORKDIR}/${PN}-client_release-${MY_PV}-${PV}"
pkg_setup() {
+ # Bug 578750
if use kernel_linux; then
linux-info_pkg_setup
if ! linux_config_exists; then
ewarn "Can't check the linux kernel configuration."
ewarn "You might be missing vsyscall support."
- else
- if kernel_is -ge 4 4 \
- && linux_chkconfig_present LEGACY_VSYSCALL_NONE \
- && ! linux_chkconfig_present X86_VSYSCALL_EMULATION; then
- ewarn "You do have neither x86 vsyscall emulation"
- ewarn "nor legacy vsyscall support enabled."
- ewarn "This will prevent some boinc projects from running."
- ewarn "Please enable vsyscall emulation:"
- ewarn " CONFIG_X86_VSYSCALL_EMULATION=y"
- ewarn "in /usr/src/linux/.config, to be found at"
- ewarn " Processor type and features --->"
- ewarn " [*] Enable vsyscall emulation"
- ewarn "or set"
- ewarn " CONFIG_LEGACY_VSYSCALL_EMULATE=y"
- ewarn "in /usr/src/linux/.config, to be found at"
- ewarn " Processor type and features --->"
- ewarn " vsyscall table for legacy applications (None) --->"
- ewarn " (X) Emulate"
- ewarn "Alternatively, you can enable CONFIG_LEGACY_VSYSCALL_NATIVE."
- ewarn "However, this has security implications and is not recommended."
- fi
+ elif kernel_is -ge 4 4 \
+ && linux_chkconfig_present LEGACY_VSYSCALL_NONE; then
+ ewarn "You do not have vsyscall emulation enabled."
+ ewarn "This will prevent some boinc projects from running."
+ ewarn "Please enable vsyscall emulation:"
+ ewarn " CONFIG_LEGACY_VSYSCALL_EMULATE=y"
+ ewarn "in /usr/src/linux/.config, to be found at"
+ ewarn " Processor type and features --->"
+ ewarn " vsyscall table for legacy applications (None) --->"
+ ewarn " (X) Emulate"
+ ewarn "Alternatively, you can enable CONFIG_LEGACY_VSYSCALL_NATIVE."
+ ewarn "However, this has security implications and is not recommended."
fi
fi
}
next reply other threads:[~2016-05-07 22:32 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-07 22:32 David Seifert [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-22 19:14 [gentoo-commits] repo/gentoo:master commit in: sci-misc/boinc/ Pacho Ramos
2024-04-12 13:08 Joonas Niilola
2024-04-11 21:34 Sam James
2024-04-11 16:46 Sam James
2024-04-11 16:37 Arthur Zamarin
2023-11-25 5:46 Sam James
2023-10-17 7:29 Andrew Ammerlaan
2023-10-17 7:29 Andrew Ammerlaan
2023-09-25 8:06 Andrew Ammerlaan
2023-06-09 15:45 Arthur Zamarin
2023-06-09 14:29 Sam James
2023-06-09 14:10 Arthur Zamarin
2023-06-03 11:15 Arthur Zamarin
2023-05-06 9:51 Arthur Zamarin
2023-04-14 19:45 Sam James
2023-04-14 19:45 Sam James
2023-04-14 19:33 Sam James
2023-04-14 19:33 Sam James
2023-04-14 19:09 Florian Schmaus
2023-04-14 8:58 Arthur Zamarin
2022-12-30 23:39 Conrad Kostecki
2022-08-09 13:12 Craig Andrews
2022-08-01 8:35 Florian Schmaus
2022-08-01 8:35 Florian Schmaus
2022-08-01 8:35 Florian Schmaus
2022-08-01 8:35 Florian Schmaus
2022-08-01 8:35 Florian Schmaus
2022-04-25 6:37 Florian Schmaus
2022-04-23 10:33 Joonas Niilola
2022-04-23 10:24 Florian Schmaus
2022-04-23 10:24 Florian Schmaus
2022-04-23 10:24 Florian Schmaus
2021-10-06 8:33 Jakov Smolić
2021-07-08 9:38 Joonas Niilola
2021-07-08 9:38 Joonas Niilola
2021-07-08 9:38 Joonas Niilola
2021-05-01 18:07 Sam James
2021-04-24 12:52 David Seifert
2021-04-24 12:52 David Seifert
2021-04-24 12:52 David Seifert
2021-04-04 20:21 David Seifert
2021-01-30 10:26 Sam James
2021-01-18 13:38 Joonas Niilola
2021-01-18 13:38 Joonas Niilola
2021-01-18 13:38 Joonas Niilola
2020-08-24 17:45 Jonas Stein
2018-12-06 21:20 Craig Andrews
2018-12-06 21:20 Craig Andrews
2018-04-24 21:57 Andreas Sturmlechner
2018-02-11 11:12 Michał Górny
2017-12-27 11:56 Mart Raudsepp
2017-12-27 11:56 Mart Raudsepp
2017-12-21 10:47 Mart Raudsepp
2017-12-21 10:47 Mart Raudsepp
2017-12-20 20:13 Craig Andrews
2017-11-02 11:39 Mart Raudsepp
2017-09-22 13:48 Michael Palimaka
2017-08-19 19:01 Michał Górny
2017-08-19 19:01 Michał Górny
2017-06-09 15:57 Anthony G. Basile
2017-06-04 17:03 Michał Górny
2017-02-17 11:28 Michael Palimaka
2017-01-04 13:42 David Seifert
2017-01-04 13:42 David Seifert
2016-11-12 15:39 David Seifert
2016-11-12 15:39 David Seifert
2016-11-12 15:39 David Seifert
2016-06-14 19:10 David Seifert
2016-06-14 19:10 David Seifert
2016-06-14 19:10 David Seifert
2016-05-07 22:32 David Seifert
2016-05-07 22:32 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-05-04 22:01 David Seifert
2016-03-20 20:08 David Seifert
2015-09-09 18:53 Michał Górny
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1462660308.87fb055e1198f9f343c3f2991154f323d7187e60.soap@gentoo \
--to=soap@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox