public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/swig/
Date: Sun, 22 Sep 2024 13:59:35 +0000 (UTC)	[thread overview]
Message-ID: <1727013502.228410dfe66b2f9b6c738675c1ad5656d9235aed.sam@gentoo> (raw)

commit:     228410dfe66b2f9b6c738675c1ad5656d9235aed
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 22 13:58:22 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Sep 22 13:58:22 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=228410df

dev-lang/swig: build with -fPIC, not -fpic

This fixes tests on hppa, sparc.

Closes: https://bugs.gentoo.org/900769
Closes: https://bugs.gentoo.org/935318
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-lang/swig/swig-4.2.1.ebuild | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/dev-lang/swig/swig-4.2.1.ebuild b/dev-lang/swig/swig-4.2.1.ebuild
index 1375557b544c..114ecb465943 100644
--- a/dev-lang/swig/swig-4.2.1.ebuild
+++ b/dev-lang/swig/swig-4.2.1.ebuild
@@ -27,6 +27,17 @@ BDEPEND="virtual/pkgconfig"
 
 DOCS=( ANNOUNCE CHANGES CHANGES.current README TODO )
 
+PATCHES=(
+	"${FILESDIR}"/${P}-tests-fpic.patch
+)
+
+src_prepare() {
+	default
+
+	# Delete after 4.2.1 (bug #900769, bug #935318)
+	sed -i -e 's:fpic:fPIC:' configure.ac configure || die
+}
+
 src_configure() {
 	# TODO: add USE for various langs? (https://bugs.gentoo.org/921504#c3)
 	econf \


             reply	other threads:[~2024-09-22 13:59 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-22 13:59 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-23 10:59 [gentoo-commits] repo/gentoo:master commit in: dev-lang/swig/ Sam James
2024-09-22 14:02 Sam James
2024-09-22 14:02 Sam James
2024-08-09  8:50 Jakov Smolić
2024-07-02  3:56 Ionen Wolkens
2024-06-08  5:18 Arthur Zamarin
2024-06-07 15:38 Arthur Zamarin
2024-05-28 13:19 Sam James
2024-02-27 22:06 Sam James
2024-01-02  7:56 Sam James
2023-06-10 21:34 Sam James
2023-06-10 21:34 Sam James
2023-06-10 21:34 Sam James
2023-06-10 21:33 Sam James
2023-01-30 16:31 Arthur Zamarin
2023-01-28 21:49 Jakov Smolić
2023-01-28  1:33 Sam James
2023-01-28  1:33 Sam James
2023-01-28  0:55 Sam James
2023-01-13 14:53 Sam James
2022-11-30 23:53 Sam James
2022-11-30 23:53 Sam James
2022-11-02  0:47 Sam James
2022-10-25 10:44 Sam James
2022-07-10  7:53 Sam James
2022-07-06  8:24 David Seifert
2021-08-16 20:35 James Le Cuirot
2021-06-18 21:07 David Seifert
2020-12-27 14:08 Fabian Groffen
2020-10-10 13:43 Sergei Trofimovich
2020-10-07  7:09 Agostino Sarubbo
2020-10-07  6:54 Agostino Sarubbo
2020-10-07  6:53 Agostino Sarubbo
2020-10-07  6:50 Agostino Sarubbo
2020-10-07  6:42 Agostino Sarubbo
2020-10-06 13:17 Sam James
2020-10-06  4:51 Sam James
2020-09-05  2:35 Sam James
2020-09-03 14:29 Thomas Deutschmann
2020-09-01  3:02 Sam James
2020-09-01  3:02 Sam James
2020-09-01  3:02 Sam James
2020-08-30 17:37 Dennis Lamm
2020-05-22  0:02 Mike Frysinger
2019-12-14 22:16 David Seifert
2019-06-30  7:46 Amy Liffey
2019-06-30  7:46 Amy Liffey
2019-06-14  1:26 Göktürk Yüksek
2019-06-06 10:04 Michael Haubenwallner
2018-06-30 13:32 David Seifert
2018-05-04 13:57 Mart Raudsepp
2018-03-10 12:23 Pacho Ramos
2018-01-21  0:41 Andreas Hüttel
2017-06-10 15:10 Agostino Sarubbo
2017-05-05 19:10 Markus Meier
2017-04-29 12:14 Jeroen Roovers
2017-04-22  7:33 Tobias Klausmann
2017-02-02 14:11 Tim Harder
2017-01-20 23:42 Tim Harder
2016-12-19 11:43 Aaron Bauman
2016-11-02 18:08 Markus Meier
2016-10-03 12:15 Tobias Klausmann
2016-10-02 10:10 Jeroen Roovers
2016-10-02  6:00 Jeroen Roovers
2016-06-19  4:23 Tim Harder
2016-06-19  4:23 Tim Harder
2016-01-11  4:20 Tim Harder
2015-08-25  4:31 Tim Harder

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=1727013502.228410dfe66b2f9b6c738675c1ad5656d9235aed.sam@gentoo \
    --to=sam@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