public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Michal Schmidt <mschmidt@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/prrte] rawhide: Waive rpminspect annocheck lto check
Date: Fri, 18 Sep 2026 23:40:37 GMT [thread overview]
Message-ID: <178977483741.1.13193734738491964358.rpms-prrte-4add1ed2de11@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/prrte
Branch : rawhide
Commit : 4add1ed2de11648747ae25ae77a62dd3dd074c5c
Author : Michal Schmidt <mschmidt@redhat.com>
Date : 2026-09-14T10:02:14+02:00
Stats : +13/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/prrte/c/4add1ed2de11648747ae25ae77a62dd3dd074c5c?branch=rawhide
Log:
Waive rpminspect annocheck lto check
PRRTE's configure deliberately strips all -flto* flags because LTO's
whole-program view conflicts with PRRTE's MCA plugin architecture
(components are dlopen()'d at runtime). None of PRRTE's binaries are
ever built with LTO by design, so skip annocheck's lto test rather
than waiving it file by file.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
diff --git a/rpminspect.yaml b/rpminspect.yaml
index 5a206dc..4ed7d02 100644
--- a/rpminspect.yaml
+++ b/rpminspect.yaml
@@ -1,4 +1,17 @@
---
+# PRRTE's configure explicitly strips all -flto* flags (see
+# _PRTE_CHECK_LTO_FLAG in config/prte_check_cflags.m4) because LTO's
+# whole-program view conflicts with PRRTE's MCA plugin architecture,
+# where components are dlopen()'d at runtime. So none of PRRTE's
+# binaries are ever built with LTO, by design. Skip annocheck's lto
+# test rather than waiving it file by file.
+# TODO: Try to remove this in the future after rebasing to at least upstream
+# v4.0.0 containing commit 2f9b12bee564 ("Add static component pointers")
+# and building against PMIx with PMIX_CAP_LTO capability in pmix_version.h.
+annocheck:
+ jobs:
+ - hardened: --skip-lto
+
# prrte's oob/tcp and ras/slurm components use legacy IPv4-only functions
# (src/mca/oob/tcp/oob_tcp_component.c, src/mca/ras/slurm/ras_slurm_module.c).
# These are upstream code paths that would need a real IPv6-aware rewrite
reply other threads:[~2026-09-18 23:40 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=178977483741.1.13193734738491964358.rpms-prrte-4add1ed2de11@fedoraproject.org \
--to=mschmidt@redhat.com \
--cc=git-commits@fedoraproject.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