From: "Hans de Graaff" <graaff@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-ruby/msgpack/
Date: Mon, 30 May 2016 18:15:24 +0000 (UTC) [thread overview]
Message-ID: <1464631892.d17d7558719411a598eddf1147b4c6b4a2b9b163.graaff@gentoo> (raw)
commit: d17d7558719411a598eddf1147b4c6b4a2b9b163
Author: Hans de Graaff <graaff <AT> gentoo <DOT> org>
AuthorDate: Mon May 30 18:05:42 2016 +0000
Commit: Hans de Graaff <graaff <AT> gentoo <DOT> org>
CommitDate: Mon May 30 18:11:32 2016 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d17d7558
dev-ruby/msgpack: fix compilation on x86
Fix bug 582968 by avoiding the default --no-undefined linker
flag. This is only an issue on 32bit arches due to a difference
in inlining rb_num2int.
Package-Manager: portage-2.2.28
dev-ruby/msgpack/msgpack-0.7.6.ebuild | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/dev-ruby/msgpack/msgpack-0.7.6.ebuild b/dev-ruby/msgpack/msgpack-0.7.6.ebuild
index 268ddc8..fc0ae75 100644
--- a/dev-ruby/msgpack/msgpack-0.7.6.ebuild
+++ b/dev-ruby/msgpack/msgpack-0.7.6.ebuild
@@ -33,6 +33,10 @@ all_ruby_prepare() {
each_ruby_configure() {
${RUBY} -Cext/${PN} extconf.rb || die "Configuration of extension failed."
+
+ # rb_num2int is not inlined on 32 bit arches but also not explicitly
+ # defined, bug 582968
+ sed -i -e 's:-Wl,--no-undefined::' ext/${PN}/Makefile || die
}
each_ruby_compile() {
next reply other threads:[~2016-05-30 18:15 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 18:15 Hans de Graaff [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-01 16:31 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/msgpack/ Hans de Graaff
2025-02-07 5:58 Hans de Graaff
2024-11-12 10:46 Hans de Graaff
2024-11-12 10:46 Hans de Graaff
2024-11-02 11:45 Arthur Zamarin
2024-10-30 15:46 Arthur Zamarin
2024-10-30 14:41 Sam James
2024-10-30 11:07 Sam James
2024-10-30 11:07 Sam James
2024-10-30 11:07 Sam James
2024-10-05 7:00 Hans de Graaff
2024-10-05 7:00 Hans de Graaff
2024-06-01 5:41 Hans de Graaff
2023-12-31 17:15 Hans de Graaff
2023-12-06 17:57 Ionen Wolkens
2023-11-24 9:31 Sam James
2023-11-23 21:09 Sam James
2023-11-23 17:12 Sam James
2023-11-15 18:39 Arthur Zamarin
2023-11-15 17:49 Jakov Smolić
2023-07-19 5:26 Hans de Graaff
2023-07-11 9:43 Hans de Graaff
2023-07-02 7:49 Hans de Graaff
2023-06-06 13:40 Hans de Graaff
2023-03-18 23:12 Sam James
2022-10-01 7:06 Hans de Graaff
2022-08-26 11:45 Hans de Graaff
2022-08-26 11:45 Hans de Graaff
2022-07-26 6:45 Hans de Graaff
2022-07-06 5:28 Hans de Graaff
2022-06-25 8:55 Hans de Graaff
2022-05-28 5:39 Hans de Graaff
2022-05-28 5:39 Hans de Graaff
2022-04-09 7:38 Hans de Graaff
2022-03-17 6:40 Hans de Graaff
2022-02-05 6:57 Hans de Graaff
2022-01-30 8:19 Hans de Graaff
2022-01-20 6:40 Hans de Graaff
2021-10-27 11:26 Hans de Graaff
2021-04-02 11:16 Hans de Graaff
2021-02-07 8:24 Hans de Graaff
2020-08-08 6:37 Hans de Graaff
2020-02-05 6:16 Hans de Graaff
2019-08-05 5:17 Hans de Graaff
2019-08-05 5:17 Hans de Graaff
2019-06-21 6:05 Hans de Graaff
2019-05-07 5:16 Hans de Graaff
2019-05-07 5:16 Hans de Graaff
2019-03-11 6:25 Hans de Graaff
2019-03-01 6:09 Hans de Graaff
2019-03-01 6:09 Hans de Graaff
2019-01-09 9:12 Hans de Graaff
2018-04-06 4:54 Hans de Graaff
2018-03-03 6:41 Hans de Graaff
2018-02-04 15:15 Hans de Graaff
2018-01-12 6:01 Hans de Graaff
2018-01-12 6:01 Hans de Graaff
2017-12-07 6:36 Hans de Graaff
2017-10-28 16:23 Andreas Sturmlechner
2017-09-10 7:53 Hans de Graaff
2017-03-07 6:01 Hans de Graaff
2017-01-28 6:48 Hans de Graaff
2016-11-14 6:39 Hans de Graaff
2016-11-14 6:39 Hans de Graaff
2016-10-17 5:23 Hans de Graaff
2016-08-22 19:15 Ole Reifschneider
2016-05-30 18:15 Hans de Graaff
2016-05-11 4:55 Hans de Graaff
2016-04-06 5:13 Hans de Graaff
2016-04-06 5:13 Hans de Graaff
2016-01-10 7:28 Hans de Graaff
2016-01-10 7:28 Hans de Graaff
2015-11-24 7:00 Hans de Graaff
2015-10-25 8:30 Hans de Graaff
2015-10-25 8:30 Hans de Graaff
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=1464631892.d17d7558719411a598eddf1147b4c6b4a2b9b163.graaff@gentoo \
--to=graaff@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