From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-admin/tripwire/
Date: Tue, 15 Jun 2021 01:22:11 +0000 (UTC) [thread overview]
Message-ID: <1623720096.cd260d9a9fdb2c2a8f0ef7b4e947c7df0ef1d2a2.sam@gentoo> (raw)
commit: cd260d9a9fdb2c2a8f0ef7b4e947c7df0ef1d2a2
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 15 01:21:32 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jun 15 01:21:36 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cd260d9a
app-admin/tripwire: update EAPI 6 -> 7, workaround GCC 11 failure
Set C++ standard to c++14 rather than perform a huge sed on the byte type.
Closes: https://bugs.gentoo.org/786465
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-admin/tripwire/tripwire-2.4.3.7.ebuild | 15 ++++++++++++---
1 file changed, 12 insertions(+), 3 deletions(-)
diff --git a/app-admin/tripwire/tripwire-2.4.3.7.ebuild b/app-admin/tripwire/tripwire-2.4.3.7.ebuild
index 423a09ff991..306f4125452 100644
--- a/app-admin/tripwire/tripwire-2.4.3.7.ebuild
+++ b/app-admin/tripwire/tripwire-2.4.3.7.ebuild
@@ -1,7 +1,7 @@
# Copyright 1999-2021 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
-EAPI=6
+EAPI=7
inherit autotools flag-o-matic
@@ -36,8 +36,17 @@ src_configure() {
# see #32613, #45823, and others.
# -taviso@gentoo.org
strip-flags
- append-cppflags -DCONFIG_DIR='"\"/etc/tripwire\""' -fno-strict-aliasing
- econf $(use_enable ssl openssl) $(use_enable static)
+
+ append-cppflags -DCONFIG_DIR='"\"/etc/tripwire\""'
+ append-cflags -fno-strict-aliasing
+
+ # "integer.cpp:1162:24: error: reference to ‘byte’ is ambiguous"
+ # bug #786465
+ append-cxxflags -std=c++14
+
+ econf \
+ $(use_enable ssl openssl) \
+ $(use_enable static)
}
src_install() {
next reply other threads:[~2021-06-15 1:22 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 1:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 4:45 [gentoo-commits] repo/gentoo:master commit in: app-admin/tripwire/ Sam James
2021-04-30 17:10 Mikle Kolyada
2019-01-07 17:00 Lars Wendler
2018-05-28 9:05 José María Alonso
2018-05-26 8:56 Mikle Kolyada
2018-05-04 10:52 Agostino Sarubbo
2018-05-02 16:33 Thomas Deutschmann
2018-04-01 20:39 José María Alonso
2018-04-01 20:13 José María Alonso
2017-11-10 8:30 Sergei Trofimovich
2017-11-03 11:54 Manuel Rüger
2017-11-02 21:16 Thomas Deutschmann
2017-10-02 16:03 José María Alonso
2017-05-19 8:20 José María Alonso
2017-05-18 19:14 Michael Weber
2017-05-04 15:55 Agostino Sarubbo
2017-05-04 13:07 Agostino Sarubbo
2017-05-04 8:49 José María Alonso
2017-04-29 15:02 Agostino Sarubbo
2017-04-18 21:04 José María Alonso
2017-04-17 8:02 Agostino Sarubbo
2017-04-06 7:46 José María Alonso
2017-04-05 12:55 Agostino Sarubbo
2017-04-04 13:30 José María Alonso
2017-03-06 11:23 José María Alonso
2017-02-25 10:41 José María Alonso
2017-02-02 10:40 José María Alonso
2016-06-10 15:32 Agostino Sarubbo
2016-05-19 13:04 José María Alonso
2016-05-03 10:50 José María Alonso
2016-03-21 21:31 Anthony G. Basile
2016-01-25 15:44 Agostino Sarubbo
2015-12-26 1:14 Anthony G. Basile
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=1623720096.cd260d9a9fdb2c2a8f0ef7b4e947c7df0ef1d2a2.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