From: Moreno <Moreno.Mauri@italtel.it>
To: crossgcc@sources.redhat.com
Subject: Virtual memory exhausted compiling a very large C-source
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <3A66C29A.BF6C3DD3@ic8sd2.settimo.italtel.it> (raw)
Message-ID: <20010401000000.yoS6DzFEA73eRpZFkInM9iml6Y4bJL-cNPv-XPn4oLs@z> (raw)
Hy everyone, I'm Moreno (from Italy).
I'm trying to compile a very large C-source (more than 25.000 lines !)
with xgcc.
I've this output:
<file>: In function <func>:
<file>:<line number>: virtual memory exhausted.
Reading gcc-info I've found that I can prevent the message:
"virtual memory exhausted"
linking xgcc with GNU libgmalloc.a or with gmalloc.o (taken from
Emacs 19 distribution).
I've tried to do so but the message isn't disapperead.
May someone help me ?
Thanks a lot
Moreno
e-mail: moreno.mauri@italtel.it
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 2:22 Moreno [this message]
2001-04-01 0:00 ` Moreno
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=3A66C29A.BF6C3DD3@ic8sd2.settimo.italtel.it \
--to=moreno.mauri@italtel.it \
--cc=crossgcc@sources.redhat.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).