From: Jay K <jay.krell@cornell.edu>
To: gcc <gcc@gcc.gnu.org>
Subject: http://gcc.gnu.org/install/specific.html maybe should mention memory settings for OpenBSD
Date: Tue, 24 Aug 2010 22:26:00 -0000 [thread overview]
Message-ID: <COL101-W1180E5FC9F7AFA1AA3B4D1E6830@phx.gbl> (raw)
Possibly a note for:
http://gcc.gnu.org/install/specific.html
under OpenBSD.
or just for the mail archives:
Building a *slight* fork of 4.5.1 on OpenBSD/x86 4.7 I hit
gcc -c -g -O2 -static -DIN_GCC -W -Wall -Wwrite-strings \
-Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute \
-DHAVE_CONFIG_H -I. -I. -I../../gcc-4.5/gcc -I../../gcc-4.5/gcc/. \
-I../../gcc-4.5/gcc/../include -I../../gcc-4.5/gcc/../libcpp/include \
-I/home/jay/dev2/cm3/m3-sys/m3cc/I386_OPENBSD/./gmp \
-I/home/jay/dev2/cm3/m3-sys/m3cc/gcc-4.5/gmp \
-I/home/jay/dev2/cm3/m3-sys/m3cc/I386_OPENBSD/./mpfr \
-I/home/jay/dev2/cm3/m3-sys/m3cc/gcc-4.5/mpfr \
-I/home/jay/dev2/cm3/m3-sys/m3cc/gcc-4.5/mpc/src \
-I../../gcc-4.5/gcc/../libdecnumber \
-I../../gcc-4.5/gcc/../libdecnumber/dpd -I../libdecnumber \
-I/usr/local/include insn-attrtab.c -o insn-attrtab.o
cc1: out of memory allocating 304988696 bytes after a total of 0 bytes
gmake: *** [insn-attrtab.o] Error 1
This was not a problem with 4.3.0 or 4.3.5. I don't know about 4.4.x.
We skipped them, just because we are slow and lagging.
I couldn't get ulimit to do anything as non-root. I do have swap.
I changed these from 512 to 768, probably not all of them necessary:
# pwd
/etc
# grep 768 login.conf
:datasize-max=768M:\
:datasize-cur=768M:\
:datasize-cur=768M:\
and then I can proceed.
System probably doesn't have much RAM, maybe only 512MB, so that
could be where the previous values came from. I had never touched them.
Smaller amounts of RAM seem "more normal" these days to pack
more virtual machines onto one physical system.
(Though this just an old laptop, not a virtual machine.)
- Jay
reply other threads:[~2010-08-24 20:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=COL101-W1180E5FC9F7AFA1AA3B4D1E6830@phx.gbl \
--to=jay.krell@cornell.edu \
--cc=gcc@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: 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).