public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Lucio Sauer" <watermanpaint@posteo.net>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:master commit in: sys-fs/ffmpegfs/
Date: Tue,  6 Aug 2024 14:10:50 +0000 (UTC)	[thread overview]
Message-ID: <1722910335.6e77a6a87c9e70f03a0a1ac9b367478ac5e1ff45.watermanpaint@gentoo> (raw)
Message-ID: <20240806141050.Gfse4z3YgSRZkKcQArPQ6iz6Yv-GcL44GHJY8QeWnAU@z> (raw)

commit:     6e77a6a87c9e70f03a0a1ac9b367478ac5e1ff45
Author:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
AuthorDate: Mon Aug  5 11:37:55 2024 +0000
Commit:     Lucio Sauer <watermanpaint <AT> posteo <DOT> net>
CommitDate: Tue Aug  6 02:12:15 2024 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=6e77a6a8

sys-fs/ffmpegfs: remove build system -D_FORTIFY_SOURCE=2

We handle it downstream.
No revbump needed since vanilla Gentoo enables these by default (as of
23.0 profiles)
https://wiki.gentoo.org/wiki/Hardened/Toolchain#Changes

Closes: https://bugs.gentoo.org/936615
Signed-off-by: Lucio Sauer <watermanpaint <AT> posteo.net>

 sys-fs/ffmpegfs/ffmpegfs-2.16-r1.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/sys-fs/ffmpegfs/ffmpegfs-2.16-r1.ebuild b/sys-fs/ffmpegfs/ffmpegfs-2.16-r1.ebuild
index 33dbbffbb..dab7b1dff 100644
--- a/sys-fs/ffmpegfs/ffmpegfs-2.16-r1.ebuild
+++ b/sys-fs/ffmpegfs/ffmpegfs-2.16-r1.ebuild
@@ -40,6 +40,8 @@ PATCHES=(
 
 src_prepare() {
 	default
+	# bug 936615
+	sed 's/-D_FORTIFY_SOURCE=2//' -i Makefile.am || die
 	eautoreconf
 }
 


             reply	other threads:[~2024-08-06 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06  2:13 Lucio Sauer [this message]
2024-08-06 14:10 ` [gentoo-commits] repo/proj/guru:master commit in: sys-fs/ffmpegfs/ Lucio Sauer
  -- strict thread matches above, loose matches on Subject: below --
2024-11-28 23:55 [gentoo-commits] repo/proj/guru:dev " Alexey Sokolov
2024-07-19  8:12 Alexey Sokolov
2024-07-11 16:43 Alexey Sokolov

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=1722910335.6e77a6a87c9e70f03a0a1ac9b367478ac5e1ff45.watermanpaint@gentoo \
    --to=watermanpaint@posteo.net \
    --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