From: David Haller <gentoo@dhaller.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-lang/solidity
Date: Thu, 13 Sep 2018 22:41:03 +0200 [thread overview]
Message-ID: <20180913204103.fflyersuy5jedv27@grusum.endjinn.de> (raw)
In-Reply-To: <1536821584.1275.0.camel@gentoo.org>
Hello,
On Thu, 13 Sep 2018, Michal Górny wrote:
># Michal Górny <mgorny@gentoo.org> (13 Sep 2018)
># Depends on old version of dev-libs/jsoncpp, blocking its pruning.
># Downstream maintainer is inactive to bump it. Removal in 30 days.
>dev-lang/solidity
As per the "no -Werror" policy, the following patch to the ebuild, or
something to the same effect should be done anyway, and it compiles
without '-Werror'.
====
--- a/solidity-0.4.18.ebuild 2017-12-20 21:09:16.000000000 +0100
+++ b/solidity-0.4.18.ebuild 2018-09-13 15:59:06.584892127 +0200
@@ -28,6 +28,11 @@
"${FILESDIR}"/${P}-fix-cmake-external-jsoncpp.diff
)
+src_prepare() {
+ sed -i '/add_compile_options(-Werror)/d' cmake/EthCompilerSettings.cmake
+ cmake-utils_src_prepare
+}
+
src_configure() {
local mycmakeargs=(
"-DBoost_USE_STATIC_LIBS=off"
====
HTH,
-dnh
--
| Ceci n'est pas une pipe
prev parent reply other threads:[~2018-09-13 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 6:53 [gentoo-dev] Last rites: dev-lang/solidity Michał Górny
2018-09-13 20:41 ` David Haller [this message]
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=20180913204103.fflyersuy5jedv27@grusum.endjinn.de \
--to=gentoo@dhaller.de \
--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