From: "Andreas Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/
Date: Wed, 25 Oct 2017 13:53:33 +0000 (UTC) [thread overview]
Message-ID: <1508939586.3372a5ecbeaa719f733cccf67caf8f96b61f3d2c.dilfridge@gentoo> (raw)
commit: 3372a5ecbeaa719f733cccf67caf8f96b61f3d2c
Author: Andreas K. Huettel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 25 13:53:06 2017 +0000
Commit: Andreas Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Wed Oct 25 13:53:06 2017 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3372a5ec
dev-lisp/clisp: Use correct gcc option, bug 635386
Shame on me for only testing with gcc-6. Let's see
what explodes next.
Closes: https://bugs.gentoo.org/635386
Package-Manager: Portage-2.3.12, Repoman-2.3.3
dev-lisp/clisp/clisp-2.49-r101.ebuild | 2 +-
dev-lisp/clisp/clisp-2.49-r9.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/dev-lisp/clisp/clisp-2.49-r101.ebuild b/dev-lisp/clisp/clisp-2.49-r101.ebuild
index 7cf1812267c..8948b19aea6 100644
--- a/dev-lisp/clisp/clisp-2.49-r101.ebuild
+++ b/dev-lisp/clisp/clisp-2.49-r101.ebuild
@@ -67,7 +67,7 @@ src_prepare() {
src_configure() {
# Bug 618170. If anyone has a better idea...
- append-flags -no-pie
+ append-flags -fno-pie
# We need this to build on alpha/ia64
if use alpha || use ia64; then
diff --git a/dev-lisp/clisp/clisp-2.49-r9.ebuild b/dev-lisp/clisp/clisp-2.49-r9.ebuild
index 017287c7dd4..d811dd15026 100644
--- a/dev-lisp/clisp/clisp-2.49-r9.ebuild
+++ b/dev-lisp/clisp/clisp-2.49-r9.ebuild
@@ -65,7 +65,7 @@ src_prepare() {
src_configure() {
# Bug 618170. If anyone has a better idea...
- append-flags -no-pie
+ append-flags -fno-pie
# We need this to build on alpha/ia64
if use alpha || use ia64; then
next reply other threads:[~2017-10-25 13:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 13:53 Andreas Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-02 4:32 [gentoo-commits] repo/gentoo:master commit in: dev-lisp/clisp/ Sam James
2024-05-02 4:32 Sam James
2023-09-16 14:06 Ulrich Müller
2022-10-15 15:13 Sam James
2022-05-14 21:52 Jakov Smolić
2022-04-28 15:05 Jakov Smolić
2022-02-28 5:04 Sam James
2022-02-28 5:03 Sam James
2022-02-17 11:00 Jakov Smolić
2022-01-19 1:12 Sam James
2021-06-03 19:15 Sam James
2020-10-10 17:55 Pacho Ramos
2019-06-16 18:30 Ulrich Müller
2019-06-16 17:15 Tobias Klausmann
2019-06-14 15:01 Agostino Sarubbo
2019-06-14 9:26 Agostino Sarubbo
2019-06-14 9:25 Agostino Sarubbo
2019-06-14 9:18 Agostino Sarubbo
2018-10-16 9:18 Tobias Klausmann
2018-08-19 22:52 Patrice Clement
2018-08-19 22:52 Patrice Clement
2018-05-12 0:32 Matt Turner
2018-04-20 8:02 David Seifert
2018-03-28 14:47 José María Alonso
2018-03-25 1:30 Sergei Trofimovich
2018-03-18 18:04 David Seifert
2018-03-08 9:29 José María Alonso
2018-03-07 12:45 José María Alonso
2018-03-07 9:36 José María Alonso
2018-03-06 15:35 José María Alonso
2018-03-05 17:21 José María Alonso
2018-03-05 16:17 José María Alonso
2017-10-24 18:47 Andreas Hüttel
2016-12-18 4:54 Andrey Grozin
2016-10-12 18:11 Pacho Ramos
2016-10-02 2:55 Andrey Grozin
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=1508939586.3372a5ecbeaa719f733cccf67caf8f96b61f3d2c.dilfridge@gentoo \
--to=dilfridge@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