From: bar.hofesh@safe-t.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:71758] [Ruby trunk - Bug #11753] Building ruby-git on Arch Linux eats all memory on ./configure
Date: Mon, 30 Nov 2015 14:45:26 +0000 [thread overview]
Message-ID: <redmine.journal-55168.20151130144525.3731437f6a55e916@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11753.20151130142733@ruby-lang.org
Issue #11753 has been updated by Bar Hofesh.
Bar Hofesh wrote:
> Hi,
>
> I'm trying to build Ruby from sources.
>
> What I tried:
>
> 1) Build from git using git clone, autoconf, ./configure
> 2) Build with RVM versions 2.2.1, 2.2-head, 2.1.5, ruby-head
>
> All have failed when reaching the "./configure" phase.
> It seems that all memory is getting eat up and the system hangs unless a quick "Ctrl + C" is pressed to stop the process.
>
> Notes:
>
> * I had ruby installed and working until trying to re-build
> * I had a system restore which left most of /home/ with wrong permissions (was taken care of but maybe Ruby's configure needs some files with +x which don't have them right now?)
> * Other programs which relays on "./configure" scripts work and build without issues.
Ok, using the "echo here and there" debug method I got to the part where it is getting stuck:
`
# Use a proper internal environment variable to ensure we don't fall
# into an infinite loop, continuously re-executing ourselves.
echo "Testing 1"
if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then
_as_can_reexec=no; export _as_can_reexec;
echo "Testing 2"
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.`
I see "Testing 1"
But not "Testing 2"
----------------------------------------
Bug #11753: Building ruby-git on Arch Linux eats all memory on ./configure
https://bugs.ruby-lang.org/issues/11753#change-55168
* Author: Bar Hofesh
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v:
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
Hi,
I'm trying to build Ruby from sources.
What I tried:
1) Build from git using git clone, autoconf, ./configure
2) Build with RVM versions 2.2.1, 2.2-head, 2.1.5, ruby-head
All have failed when reaching the "./configure" phase.
It seems that all memory is getting eat up and the system hangs unless a quick "Ctrl + C" is pressed to stop the process.
Notes:
* I had ruby installed and working until trying to re-build
* I had a system restore which left most of /home/ with wrong permissions (was taken care of but maybe Ruby's configure needs some files with +x which don't have them right now?)
* Other programs which relays on "./configure" scripts work and build without issues.
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2015-11-30 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11753.20151130142733@ruby-lang.org>
2015-11-30 14:27 ` [ruby-core:71757] [Ruby trunk - Bug #11753] [Open] Building ruby-git on Arch Linux eats all memory on ./configure bar.hofesh
2015-11-30 14:45 ` bar.hofesh [this message]
2015-12-01 4:13 ` [ruby-core:71768] [Ruby trunk - Bug #11753] [Third Party's Issue] " 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.journal-55168.20151130144525.3731437f6a55e916@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).