From: Sean Young <sean@mess.org>
To: linux-media@vger.kernel.org
Subject: [PATCH v4l-utils] keytable: do not install bpf protocols decoders with execute permission
Date: Fri, 23 Nov 2018 11:53:51 +0000 [thread overview]
Message-ID: <20181123115351.13856-1-sean@mess.org> (raw)
The rpm packaging system will try to extract debug information, which
fails since there is no build id. This can be avoided by removing
the execute permission.
BPF relocatable files are executable anyway so this is the right
thing to do.
See:
https://github.com/rpm-software-management/rpm/pull/604
Signed-off-by: Sean Young <sean@mess.org>
---
utils/keytable/bpf_protocols/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/utils/keytable/bpf_protocols/Makefile.am b/utils/keytable/bpf_protocols/Makefile.am
index 1b90411b..d1f04cb4 100644
--- a/utils/keytable/bpf_protocols/Makefile.am
+++ b/utils/keytable/bpf_protocols/Makefile.am
@@ -21,4 +21,4 @@ EXTRA_DIST = $(PROTOCOLS:%.o=%.c) bpf_helpers.h
install-data-local:
$(install_sh) -d "$(DESTDIR)$(keytableuserdir)/protocols"
$(install_sh) -d "$(DESTDIR)$(keytablesystemdir)/protocols"
- $(install_sh) $(PROTOCOLS) "$(DESTDIR)$(keytablesystemdir)/protocols"
+ $(install_sh) -m 0644 $(PROTOCOLS) "$(DESTDIR)$(keytablesystemdir)/protocols"
--
2.19.1
reply other threads:[~2018-11-23 22:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181123115351.13856-1-sean@mess.org \
--to=sean@mess.org \
--cc=linux-media@vger.kernel.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).