From: Takahiro Kambe <taca@back-street•net>
To: ruby-dev@ruby-lang.org
Subject: [ruby-dev:50465] Re: [Ruby trunk Bug#14439] build failed on NetBSD 7.1 with MJIT
Date: Sun, 04 Feb 2018 21:47:22 +0900 (JST) [thread overview]
Message-ID: <20180204.214722.928776197218836667.taca@back-street.net> (raw)
In-Reply-To: <redmine.issue-14439.20180204122852.8b177c62b00fc2c1@ruby-lang.org>
In message <redmine.issue-14439.20180204122852.8b177c62b00fc2c1@ruby-lang.org>
on Sun, 04 Feb 2018 12:28:54 +0000 (UTC),
usa@garbagecollect•jp wrote:
> というわけで手元のNetBSD/i386 7.1で試そうとしたら、残念ながらビルドエラーになりました。
http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/lang/ruby25-base/patches/patch-configure?rev=1.4
の、
@@ -20224,6 +20229,8 @@ else
# ifdef _MSC_VER
# include <malloc.h>
# define alloca _alloca
+# elif defined(__NetBSD__) || defined(__FreeBSD__) || defined(__DragonFly__) || defined(__OpenBSD__)
+# include <stdlib.h>
# else
# ifdef HAVE_ALLOCA_H
# include <alloca.h>
辺りでしょうか?
--
神戸 隆博 / Takahiro Kambe
next prev parent reply other threads:[~2018-02-04 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-14439.20180204122852@ruby-lang.org>
2018-02-04 12:28 ` [ruby-dev:50464] [Ruby trunk Bug#14439] build failed on NetBSD 7.1 with MJIT usa
2018-02-04 12:47 ` Takahiro Kambe [this message]
2018-02-04 12:52 ` [ruby-dev:50466] " usa
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=20180204.214722.928776197218836667.taca@back-street.net \
--to=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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).