From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lua/luafilesystem/
Date: Thu, 12 Nov 2015 23:01:16 +0000 (UTC) [thread overview]
Message-ID: <1447369253.4735f1fb8896147f9ed04235226b7ef69c789bb9.zmedico@gentoo> (raw)
commit: 4735f1fb8896147f9ed04235226b7ef69c789bb9
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Thu Nov 12 23:00:34 2015 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Thu Nov 12 23:00:53 2015 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4735f1fb
dev-lua/luafilesystem: tweak gcc sed expression to avoid CFLAGS match
This will prevent -frecord-gcc-switches in CFLAGS from being matched
by the "s|gcc|$(tc-getCC)|" sed expression.
Package-Manager: portage-2.2.24
dev-lua/luafilesystem/luafilesystem-1.5.0.ebuild | 2 +-
dev-lua/luafilesystem/luafilesystem-1.6.2.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-lua/luafilesystem/luafilesystem-1.5.0.ebuild b/dev-lua/luafilesystem/luafilesystem-1.5.0.ebuild
index 5d96c62..803696f 100644
--- a/dev-lua/luafilesystem/luafilesystem-1.5.0.ebuild
+++ b/dev-lua/luafilesystem/luafilesystem-1.5.0.ebuild
@@ -19,11 +19,11 @@ RDEPEND="${DEPEND}"
src_prepare() {
sed -i \
+ -e "s|gcc|$(tc-getCC)|" \
-e "s|/usr/local|/usr|" \
-e "s|/lib|/$(get_libdir)|" \
-e "s|-O2|${CFLAGS}|" \
-e "/^LIB_OPTION/s|= |= ${LDFLAGS} |" \
- -e "s|gcc|$(tc-getCC)|" \
config || die
}
diff --git a/dev-lua/luafilesystem/luafilesystem-1.6.2.ebuild b/dev-lua/luafilesystem/luafilesystem-1.6.2.ebuild
index 53a0b21..0ef510a 100644
--- a/dev-lua/luafilesystem/luafilesystem-1.6.2.ebuild
+++ b/dev-lua/luafilesystem/luafilesystem-1.6.2.ebuild
@@ -19,11 +19,11 @@ RDEPEND="${DEPEND}"
src_prepare() {
sed -i \
+ -e "s|gcc|$(tc-getCC)|" \
-e "s|/usr/local|/usr|" \
-e "s|/lib|/$(get_libdir)|" \
-e "s|-O2|${CFLAGS}|" \
-e "/^LIB_OPTION/s|= |= ${LDFLAGS} |" \
- -e "s|gcc|$(tc-getCC)|" \
config || die
}
next reply other threads:[~2015-11-12 23:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 23:01 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-01 21:17 [gentoo-commits] repo/gentoo:master commit in: dev-lua/luafilesystem/ Patrice Clement
2017-08-15 5:41 Alexis Ballier
2018-03-27 7:31 Sergei Trofimovich
2018-04-21 22:56 Aaron Bauman
2019-05-12 20:56 Thomas Deutschmann
2019-07-29 14:41 Mikle Kolyada
2019-09-15 17:17 Michał Górny
2020-01-09 18:41 Rafael Martins
2020-03-15 23:55 Georgy Yakovlev
2020-03-15 23:55 Georgy Yakovlev
2020-10-31 22:48 Georgy Yakovlev
2020-11-23 18:48 Conrad Kostecki
2020-11-23 21:39 Conrad Kostecki
2020-11-23 21:39 Conrad Kostecki
2020-11-24 1:10 Sam James
2020-11-24 1:10 Sam James
2020-11-24 7:20 Agostino Sarubbo
2020-11-24 7:41 Agostino Sarubbo
2020-11-24 7:42 Agostino Sarubbo
2020-11-24 7:44 Agostino Sarubbo
2020-11-24 7:45 Agostino Sarubbo
2020-11-24 13:04 Conrad Kostecki
2020-11-29 15:37 Conrad Kostecki
2020-11-29 15:37 Conrad Kostecki
2021-01-23 22:42 Sam James
2021-01-23 22:51 Sam James
2021-01-27 19:48 Conrad Kostecki
2021-02-21 21:22 Conrad Kostecki
2021-04-20 21:20 Sergei Trofimovich
2021-05-25 16:21 Georgy Yakovlev
2021-09-18 12:29 Marek Szuba
2022-02-10 0:49 Sam James
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=1447369253.4735f1fb8896147f9ed04235226b7ef69c789bb9.zmedico@gentoo \
--to=zmedico@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