From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-accessibility/epos/
Date: Tue, 25 Jun 2024 07:06:26 +0000 (UTC) [thread overview]
Message-ID: <1719299165.36906132945b5acc3890065d41a0953c918b261d.sam@gentoo> (raw)
commit: 36906132945b5acc3890065d41a0953c918b261d
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 25 07:05:26 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun 25 07:06:05 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=36906132
app-accessibility/epos: pass -fno-delete-null-pointer-checks
I've no idea why the original fix didn't just get fixed up instead
of reverting it, but it is what it is.
Closes: https://bugs.gentoo.org/649858
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../epos/{epos-2.5.37-r3.ebuild => epos-2.5.37-r4.ebuild} | 3 +++
1 file changed, 3 insertions(+)
diff --git a/app-accessibility/epos/epos-2.5.37-r3.ebuild b/app-accessibility/epos/epos-2.5.37-r4.ebuild
similarity index 94%
rename from app-accessibility/epos/epos-2.5.37-r3.ebuild
rename to app-accessibility/epos/epos-2.5.37-r4.ebuild
index a25f239234a6..33aedd1f8897 100644
--- a/app-accessibility/epos/epos-2.5.37-r3.ebuild
+++ b/app-accessibility/epos/epos-2.5.37-r4.ebuild
@@ -33,6 +33,9 @@ src_prepare() {
}
src_configure() {
+ # bug #649858
+ append-flags -fno-delete-null-pointer-checks
+
# Uses removed 'register' keyword, bug #894178
append-cxxflags -std=c++03
next reply other threads:[~2024-06-25 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 7:06 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-29 6:58 [gentoo-commits] repo/gentoo:master commit in: app-accessibility/epos/ Arthur Zamarin
2023-02-13 23:24 Sam James
2020-09-19 8:04 Michał Górny
2020-03-31 18:02 Sergei Trofimovich
2018-05-25 1:58 Aaron Bauman
2018-05-24 23:32 Aaron Bauman
2018-05-24 21:58 Aaron Bauman
2018-05-24 21:58 Aaron Bauman
2017-05-04 13:32 Wolfram Schlich
2016-05-06 22:47 William Hubbs
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=1719299165.36906132945b5acc3890065d41a0953c918b261d.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