From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/pspdftool/
Date: Thu, 29 Feb 2024 23:58:15 +0000 (UTC) [thread overview]
Message-ID: <1709251059.efd1a1f09c5c37ee32ea6e1185a0d10305097ff6.sam@gentoo> (raw)
commit: efd1a1f09c5c37ee32ea6e1185a0d10305097ff6
Author: Eli Schwartz <eschwartz93 <AT> gmail <DOT> com>
AuthorDate: Thu Feb 29 22:29:27 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Feb 29 23:57:39 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=efd1a1f0
app-text/pspdftool: mark LTO-unsafe, mark strict-aliasing unsafe
The software is:
- dead upstream since 2015
- maintainer-needed in gentoo
- no reverse dependencies
- unstable-only
- a walking strict-aliasing problem
It's not getting fixed any time soon, and there's nowhere to report
its issues, so just filter out the most dangerous flags and pray nothing
explodes.
Closes: https://bugs.gentoo.org/855023
Signed-off-by: Eli Schwartz <eschwartz93 <AT> gmail.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-text/pspdftool/pspdftool-0.03.ebuild | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/app-text/pspdftool/pspdftool-0.03.ebuild b/app-text/pspdftool/pspdftool-0.03.ebuild
index 5dff5b9d0d33..97d533be413d 100644
--- a/app-text/pspdftool/pspdftool-0.03.ebuild
+++ b/app-text/pspdftool/pspdftool-0.03.ebuild
@@ -1,9 +1,9 @@
-# Copyright 1999-2020 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
-inherit autotools
+inherit autotools flag-o-matic
DESCRIPTION="Tool for prepress preparation of PDF and PostScript documents"
HOMEPAGE="https://sourceforge.net/projects/pspdftool"
@@ -24,6 +24,12 @@ src_prepare() {
}
src_configure() {
+ # -Werror=strict-aliasing; do not trust for LTO-safety either.
+ # https://bugs.gentoo.org/855023
+ # Upstream is dead for nearly a decade. Not forwarded.
+ append-flags -fno-strict-aliasing
+ filter-lto
+
econf $(use_with zlib)
}
next reply other threads:[~2024-02-29 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 23:58 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-21 21:51 [gentoo-commits] repo/gentoo:master commit in: app-text/pspdftool/ David Seifert
2020-01-21 21:51 David Seifert
2018-03-10 13:22 Pacho Ramos
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=1709251059.efd1a1f09c5c37ee32ea6e1185a0d10305097ff6.sam@gentoo \
--to=sam@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