From: gregory benison <gbenison@gmail.com>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: Halt while building guile
Date: Tue, 24 Apr 2012 07:09:29 -0700 [thread overview]
Message-ID: <CAEmW81H9Y9SyYWhSzR8KLaWJLagtPczGJvtXh+BFpqG4tCJsXw@mail.gmail.com> (raw)
In-Reply-To: <CAPjoZoeU=1bJOSeEcxkOx8Je8GH4AxabtsUTvVqhJ66TbnDyVA@mail.gmail.com>
On Fri, Mar 16, 2012 at 3:34 AM, Nala Ginrut <nalaginrut@gmail.com> wrote:
> I didn't saw any error with your information, and I think it's normal. The
> *.go compiling is very slow even if you have a good machine. So be patient.
Yes compiling these files is quite expensive and I have found that it
can run into resource limitations. A case study - I was recently
trying to install guile-2.0.5 on a shared hosting account. The build
process would always halt during compilation of eval.go due to limits
placed on memory use. The solution I eventually adopted was to steal
an already-compiled eval.go file for that architecture from a Debian
package of guile, drop that into the build tree, and restart the
building process - and it resulted in a working guile.
So while it is possible that the build issues you are seeing are due
to some kind of deadlock as others have suggested, I would not rule
out that this is a problem with some sort of resource limit and that
once you get guile compiled on your system it will function correctly
for less-demanding applications.
--
Greg Benison <gbenison@gmail.com>
[blog] http://gcbenison.wordpress.com
[twitter] @gcbenison
prev parent reply other threads:[~2012-04-24 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 9:55 Halt while building guile Kun Liang
2012-03-16 10:34 ` Nala Ginrut
2012-03-16 20:31 ` Andrew Horton
2012-04-24 14:09 ` gregory benison [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEmW81H9Y9SyYWhSzR8KLaWJLagtPczGJvtXh+BFpqG4tCJsXw@mail.gmail.com \
--to=gbenison@gmail.com \
--cc=guile-devel@gnu.org \
--cc=nalaginrut@gmail.com \
/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).