From: zmizsei@extrowerk.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:92553] [Ruby trunk Bug#15826] Haiku LIBC_SO and LIBM_SO support for test/fiddle/helper.rb
Date: Sun, 05 May 2019 15:47:54 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-15826.20190505154753.91dd76b0409357e8@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15826.20190505154753@ruby-lang.org
Issue #15826 has been reported by extrowerk (Zoltán Mizsei).
----------------------------------------
Bug #15826: Haiku LIBC_SO and LIBM_SO support for test/fiddle/helper.rb
https://bugs.ruby-lang.org/issues/15826
* Author: extrowerk (Zoltán Mizsei)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [x86_64-haiku]
* Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
This is required for the tests.
Haiku comes currently in 2 different flavour: 32 and 64 bit.
64 bit have only one toolchain, so it is easy, but 32 bit comes with 2 different (GCC2 primary and GCC7 secondary). Ruby built with GCC7 on Haiku, so it needs to pick the secondary arch libroot.so.
libroot.so is a complex lib which provides the libm and libc functionality, and probably much more.
---Files--------------------------------
ruby_test_fix.patch (692 Bytes)
--
https://bugs.ruby-lang.org/
Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
next parent reply other threads:[~2019-05-05 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15826.20190505154753@ruby-lang.org>
2019-05-05 15:47 ` zmizsei [this message]
2019-06-13 3:14 ` [ruby-core:93082] [Ruby trunk Bug#15826] Haiku LIBC_SO and LIBM_SO support for test/fiddle/helper.rb muraken
2019-06-13 3:16 ` [ruby-core:93083] " muraken
2019-06-13 5:00 ` [ruby-core:93084] " nobu
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-15826.20190505154753.91dd76b0409357e8@ruby-lang.org \
--to=ruby-core@ruby-lang.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).