public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "arno at heho dot snv dot jussieu dot fr" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/24154] Make requires too much memory building libjava Date: Thu, 22 Dec 2005 15:33:00 -0000 [thread overview] Message-ID: <20051222153317.12666.qmail@sourceware.org> (raw) In-Reply-To: <bug-24154-1313@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from arno at heho dot snv dot jussieu dot fr 2005-12-22 15:33 ------- Might this be related to make-bug #1379 ("Don't use alloca() for automatic variable values like $^, etc. In the case of very large lists of prerequisites this causes problems."), which has been solved after make-3.80 was released? At least on freebsd, I can build and install libjava by using a recent cvs-version of make ( /usr/opt/scito/make/bin/gmake --version: GNU Make 3.81beta4; This program built for i386-portbld-freebsd5.4 ), with indeed still a maximum memory usage of about 350MB; however, make-3.80 segfaults with a 'memory exhausted' error, even if I add 2Gig extra swap space. Arno -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24154
next prev parent reply other threads:[~2005-12-22 15:33 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24154-1313@http.gcc.gnu.org/bugzilla/> 2005-10-03 19:07 ` tromey at gcc dot gnu dot org 2005-12-04 18:08 ` mark at gcc dot gnu dot org 2005-12-22 15:33 ` arno at heho dot snv dot jussieu dot fr [this message] 2005-12-23 8:10 ` chat95 at mac dot com 2005-12-23 8:13 ` chat95 at mac dot com 2006-02-28 13:11 ` mark at gcc dot gnu dot org 2007-03-23 18:16 ` s_j_newbury at yahoo dot co dot uk [not found] <bug-24154-8172@http.gcc.gnu.org/bugzilla/> 2012-02-22 13:06 ` xiaoyuanbo at yeah dot net 2005-09-30 23:24 [Bug libgcj/24154] New: " ian at airs dot com 2005-10-01 8:44 ` [Bug libgcj/24154] " mark at gcc dot gnu dot org
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=20051222153317.12666.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.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: linkBe 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).