public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Gilles Dartiguelongue" <eva@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-libs/gst-plugins-ugly/
Date: Sun, 25 Oct 2015 23:01:11 +0000 (UTC)	[thread overview]
Message-ID: <1445812812.89b282f543369eb6c869e3cf82ab36b67c04322c.eva@gentoo> (raw)

commit:     89b282f543369eb6c869e3cf82ab36b67c04322c
Author:     Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 25 21:52:39 2015 +0000
Commit:     Gilles Dartiguelongue <eva <AT> gentoo <DOT> org>
CommitDate: Sun Oct 25 22:40:12 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=89b282f5

media-libs/gst-plugins-ugly: remove unneeded flag filtering

Legacy from over 10 years ago, do not seem to cause problems now and we want to avoid over filtering.

Package-Manager: portage-2.2.23

 media-libs/gst-plugins-ugly/gst-plugins-ugly-1.6.0.ebuild | 9 ---------
 1 file changed, 9 deletions(-)

diff --git a/media-libs/gst-plugins-ugly/gst-plugins-ugly-1.6.0.ebuild b/media-libs/gst-plugins-ugly/gst-plugins-ugly-1.6.0.ebuild
index 408ed6a..e40a4fb 100644
--- a/media-libs/gst-plugins-ugly/gst-plugins-ugly-1.6.0.ebuild
+++ b/media-libs/gst-plugins-ugly/gst-plugins-ugly-1.6.0.ebuild
@@ -24,15 +24,6 @@ DEPEND="${RDEPEND}
 	>=dev-util/gtk-doc-am-1.12
 "
 
-src_configure() {
-	# gst doesnt handle optimisations well
-	strip-flags
-	replace-flags "-O3" "-O2"
-	filter-flags "-fprefetch-loop-arrays" # see bug 22249
-
-	multilib-minimal_src_configure
-}
-
 multilib_src_install_all() {
 	DOCS="AUTHORS ChangeLog NEWS README RELEASE"
 	einstalldocs


             reply	other threads:[~2015-10-25 23:01 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-25 23:01 Gilles Dartiguelongue [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-25 23:01 [gentoo-commits] repo/gentoo:master commit in: media-libs/gst-plugins-ugly/ Gilles Dartiguelongue
2015-10-25 23:01 Gilles Dartiguelongue
2015-11-08 19:27 Gilles Dartiguelongue
2015-12-26 18:21 Gilles Dartiguelongue
2016-01-31 15:54 Gilles Dartiguelongue
2016-05-03 20:39 Markus Meier
2016-08-21 13:37 Gilles Dartiguelongue
2016-09-18 22:44 Gilles Dartiguelongue
2016-12-06 21:21 Markus Meier
2017-01-22 18:03 Agostino Sarubbo
2017-02-15 17:43 Markus Meier
2017-03-10  5:51 Markus Meier
2017-07-08 16:08 Sergei Trofimovich
2017-07-20  4:40 Markus Meier
2017-09-18 20:54 Mart Raudsepp
2017-09-18 20:54 Mart Raudsepp
2017-10-09 22:48 Thomas Deutschmann
2017-10-26  7:30 Sergei Trofimovich
2017-11-01  9:19 Sergei Trofimovich
2017-11-01  9:35 Sergei Trofimovich
2017-11-01 19:56 Sergei Trofimovich
2017-11-07  8:06 Sergei Trofimovich
2017-11-11 21:49 Thomas Deutschmann
2017-12-25 11:51 Markus Meier
2018-01-03 22:09 Mart Raudsepp
2018-02-04 11:48 Mart Raudsepp
2018-03-17 17:19 Mikle Kolyada
2018-03-18 19:36 Sergei Trofimovich
2018-03-28 19:24 Markus Meier
2018-06-16 18:27 Mart Raudsepp
2018-06-16 18:27 Mart Raudsepp
2018-06-18 17:19 Mart Raudsepp
2018-07-15 22:52 Mart Raudsepp
2018-07-31  7:25 Mart Raudsepp
2018-08-22  5:12 Markus Meier
2018-09-17 22:17 Mart Raudsepp
2018-09-19  8:42 Sergei Trofimovich
2018-09-21  5:32 Mart Raudsepp
2019-01-15 23:11 Mart Raudsepp
2019-02-05 23:21 Mart Raudsepp
2019-06-20 21:28 Mart Raudsepp
2020-05-03 19:12 Mart Raudsepp
2020-06-21 21:59 Mart Raudsepp
2020-08-08  3:23 Sam James
2021-02-13 17:51 Mart Raudsepp
2021-02-17 13:53 Sam James
2021-02-18  8:47 Sam James
2021-02-19 23:03 Mart Raudsepp
2021-08-10  0:02 Marek Szuba
2021-09-16  1:46 Sam James
2021-09-16 18:55 Sam James
2021-12-27 21:54 Mart Raudsepp
2021-12-28  7:25 Sam James
2022-11-02  5:50 WANG Xuerui
2022-11-20 18:34 Mart Raudsepp
2022-11-24 12:12 WANG Xuerui
2023-07-25 18:07 Arthur Zamarin
2023-10-13  7:33 Mart Raudsepp
2024-04-01 19:55 Mart Raudsepp
2024-04-30  8:28 Mart Raudsepp

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=1445812812.89b282f543369eb6c869e3cf82ab36b67c04322c.eva@gentoo \
    --to=eva@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