From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] slurm-wlm: use lazy bind (fix plugin loading)
Date: Sun, 27 Sep 2020 21:40:36 +0200 [thread overview]
Message-ID: <20200927194036.PQoP-NxvppZdDNvkJjTvklfRo5FDXRn5excNGxWWpPk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25130@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
There is an updated pull request by st3r4g against master on the void-packages repository
https://github.com/st3r4g/void-packages slurm-wlm-fix-lazy
https://github.com/void-linux/void-packages/pull/25130
slurm-wlm: use lazy bind (fix plugin loading)
fixes #25123
ping maintainer @Vaelatern
A patch file from https://github.com/void-linux/void-packages/pull/25130.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-slurm-wlm-fix-lazy-25130.patch --]
[-- Type: text/x-diff, Size: 1093 bytes --]
From 2a5aa19acec9352c905d0cbe62ed47e508243024 Mon Sep 17 00:00:00 2001
From: Stefano Ragni <st3r4g@protonmail.com>
Date: Sun, 27 Sep 2020 15:31:23 +0200
Subject: [PATCH] slurm-wlm: use lazy bind (fix plugin loading)
---
srcpkgs/slurm-wlm/template | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/srcpkgs/slurm-wlm/template b/srcpkgs/slurm-wlm/template
index 9753cabe79f..d5b5880370d 100644
--- a/srcpkgs/slurm-wlm/template
+++ b/srcpkgs/slurm-wlm/template
@@ -1,7 +1,7 @@
# Template file for 'slurm-wlm'
pkgname=slurm-wlm
version=19.05.5.1
-revision=2
+revision=3
_distver="${version//./-}"
wrksrc="slurm-slurm-${_distver}"
build_style=gnu-configure
@@ -20,6 +20,10 @@ checksum=e53e67bd0bb4c37a9c481998764a746467a96bc41d6527569080514f36452c07
CFLAGS="-fcommon"
+# Fix plugin loading. Yes, this disables hardening, this is on purpose
+# https://bugs.schedmd.com/show_bug.cgi?id=2443
+LDFLAGS="-Wl,-z,lazy"
+
if [ "$XBPS_TARGET_WORDSIZE" = "32" ]; then
# configure: error: 32-bit support is deprecated, and not tested
# regularly. Use at your own risk.
next prev parent reply other threads:[~2020-09-27 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 13:34 [PR PATCH] " st3r4g
2020-09-27 14:34 ` [PR REVIEW] " ericonr
2020-09-27 14:43 ` st3r4g
2020-09-27 14:46 ` [PR PATCH] [Updated] " st3r4g
2020-09-27 16:33 ` ericonr
2020-09-27 16:33 ` ericonr
2020-09-27 16:49 ` Vaelatern
2020-09-27 19:40 ` st3r4g [this message]
2020-09-27 19:48 ` st3r4g
2020-09-27 20:24 ` ericonr
2020-09-29 0:42 ` [PR PATCH] [Merged]: " Vaelatern
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=20200927194036.PQoP-NxvppZdDNvkJjTvklfRo5FDXRn5excNGxWWpPk@z \
--to=st3r4g@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).