sci-misc/boinc: Fix VSYSCALL check #1422
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
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
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
|
@SoapGentoo @jlec Is there something wrong with the QA check? None of these make sense and if I try to open any of the links, the page loads until time-out without showing anything... |
|
Disregard all warnings. The VM meant to be hosting our QA servers is down atm. |
monsieurp
added
bugfix
assigned
|
Merged, thanks. |
|
is closed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Gentoo-Bug: 578750
The configuration options were misunderstood.
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
@SoapGentoo @jlec I was not sure if the one-commit-per-ebuild-policy applies to such a case were all fixes are the same.