public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tim Harder" <radhermit@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/fuse-common/
Date: Mon, 19 Mar 2018 14:34:23 +0000 (UTC)	[thread overview]
Message-ID: <1521470030.21b2ec200196e4f44e2d4c91814c9fab94b6cb49.radhermit@gentoo> (raw)

commit:     21b2ec200196e4f44e2d4c91814c9fab94b6cb49
Author:     Tim Harder <radhermit <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 19 14:28:04 2018 +0000
Commit:     Tim Harder <radhermit <AT> gentoo <DOT> org>
CommitDate: Mon Mar 19 14:33:50 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=21b2ec20

sys-fs/fuse-common: filter lto from LDFLAGS as it's unsupported

Closes: https://bugs.gentoo.org/650874

 sys-fs/fuse-common/fuse-common-3.2.1.ebuild | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/sys-fs/fuse-common/fuse-common-3.2.1.ebuild b/sys-fs/fuse-common/fuse-common-3.2.1.ebuild
index 8c95a00239d..e2dc774e41a 100644
--- a/sys-fs/fuse-common/fuse-common-3.2.1.ebuild
+++ b/sys-fs/fuse-common/fuse-common-3.2.1.ebuild
@@ -3,7 +3,7 @@
 
 EAPI=6
 
-inherit meson udev
+inherit meson udev flag-o-matic
 
 DESCRIPTION="Common files for multiple slots of sys-fs/fuse"
 HOMEPAGE="https://github.com/libfuse/libfuse"
@@ -18,6 +18,13 @@ RDEPEND="!<sys-fs/fuse-2.9.7-r1:0"
 
 S=${WORKDIR}/fuse-${PV}
 
+src_prepare() {
+	default
+
+	# lto not supported yet -- https://github.com/libfuse/libfuse/issues/198
+	filter-flags -flto
+}
+
 src_install() {
 	newsbin "${BUILD_DIR}"/util/mount.fuse3 mount.fuse
 	doman doc/mount.fuse.8


             reply	other threads:[~2018-03-19 14:34 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19 14:34 Tim Harder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-19 21:05 [gentoo-commits] repo/gentoo:master commit in: sys-fs/fuse-common/ Tim Harder
2018-03-20 17:49 Tim Harder
2018-04-06 13:33 Tim Harder
2018-09-15  9:17 Tim Harder
2018-12-07  2:41 Thomas Deutschmann
2018-12-07 12:40 Mikle Kolyada
2018-12-07 20:07 Sergei Trofimovich
2018-12-08  9:23 Sergei Trofimovich
2018-12-08  9:28 Sergei Trofimovich
2018-12-08  9:36 Sergei Trofimovich
2018-12-08  9:44 Sergei Trofimovich
2018-12-08 12:21 Mikle Kolyada
2018-12-11  7:15 Tim Harder
2018-12-12  4:13 Tim Harder
2018-12-12  4:13 Tim Harder
2018-12-12  9:56 Tim Harder
2018-12-23 20:37 Tim Harder
2019-01-16 21:07 Mart Raudsepp
2019-01-30 16:04 Tobias Klausmann
2019-10-17 15:04 Göktürk Yüksek
2019-11-18 21:19 Tim Harder
2019-11-18 21:19 Tim Harder
2019-11-18 21:19 Tim Harder
2019-11-19  1:31 Aaron Bauman
2019-11-19  2:08 Aaron Bauman
2019-11-20 16:12 Mike Gilbert
2019-12-22 22:25 Thomas Deutschmann
2020-04-12  4:29 Mike Gilbert
2020-04-12 10:52 Mart Raudsepp
2020-04-13 10:16 Agostino Sarubbo
2020-04-13 10:17 Agostino Sarubbo
2020-04-13 10:19 Agostino Sarubbo
2020-04-13 13:05 Sergei Trofimovich
2020-04-13 14:48 Agostino Sarubbo
2020-04-13 14:53 Agostino Sarubbo
2020-04-19  8:38 Sergei Trofimovich
2020-06-12 22:39 Tim Harder
2020-06-12 22:39 Tim Harder
2020-08-12 10:54 Lars Wendler
2020-09-26  0:50 Sam James
2020-12-25 13:29 Thomas Deutschmann
2021-02-05 11:55 Lars Wendler
2021-05-13 16:18 Sam James
2021-05-13 16:24 Sam James
2021-05-13 17:51 Sam James
2021-05-13 17:53 Sam James
2021-05-13 18:58 Sam James
2021-05-14  9:35 Agostino Sarubbo
2021-05-14 16:19 Thomas Deutschmann
2021-05-14 22:14 David Seifert
2021-05-15 19:14 Sergei Trofimovich
2021-05-15 22:15 David Seifert
2021-06-12 17:49 Lars Wendler
2021-06-14  9:19 David Seifert
2021-08-10 15:36 Agostino Sarubbo
2021-08-11  0:02 Sam James
2021-08-11  0:12 Sam James
2021-08-11  0:24 Sam James
2021-08-11 19:11 Sam James
2021-08-11 20:14 Sam James
2021-08-13 21:54 Sam James
2021-09-04 17:35 David Seifert
2022-01-04  3:29 Sam James
2022-05-13  6:33 WANG Xuerui

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=1521470030.21b2ec200196e4f44e2d4c91814c9fab94b6cb49.radhermit@gentoo \
    --to=radhermit@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