public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Robert W. Hasker" <hasker@baobab.cs.uwplatt.edu> To: gcc-gnats@gcc.gnu.org Subject: bootstrap/7552: problems building gcc 3.1.1 with -O2 Date: Fri, 09 Aug 2002 07:16:00 -0000 [thread overview] Message-ID: <200208091404.JAA24932@baobab.cs.uwplatt.edu> (raw) >Number: 7552 >Category: bootstrap >Synopsis: "not enough virtual memory error" when building gcc-3.1.1 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 09 07:06:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Robert W. Hasker >Release: 3.1.1 >Organization: University of Wisconsin - Platteville >Environment: System: OSF1 baobab.cs.uwplatt.edu V4.0 1530 alpha Machine: alpha host: alpha-dec-osf4.0g build: alpha-dec-osf4.0g target: alpha-dec-osf4.0g configured with: ../gcc-3.1.1/configure --with-stabs --enable-languages=c,c++,f77,java >Description: When I create a separate subdirectory, ./configure, and then "make", I get the error virtual memory exhausted: Not enough space I'm mildly surprised if our VM really isn't large enough; here's part of the output of swapon -s, and at the time of the build no non-system jobs were running: Total swap allocation: Allocated space: 66034 pages (515MB) In-use space: 5095 pages ( 7%) Available space: 60939 pages ( 92%) I have also been able to build previous versions of gcc with no problems, and our javac (which is pretty memory-intensive) runs just fine. The problem occurred with the command gcc -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Icp -I../../gcc-3.1.1/gcc -I../../gcc-3.1.1/gcc/cp -I../../gcc-3.1.1/gcc/config -I../../gcc-3.1.1/gcc/../include ../../gcc-3.1.1/gcc/cp/decl.c -o cp/decl.o After changing -O2 to -O and rebuilding, I got the same problem w/ the command /usr2/sys/usr/local/src/bld311/gcc/xgcc -shared-libgcc -B/usr2/sys/usr/local/src/bld311/gcc/ -nostdinc++ -L/usr2/sys/usr/local/src/bld311/alpha-dec-osf4.0g/libstdc++-v3/src -L/usr2/sys/usr/local/src/bld311/alpha-dec-osf4.0g/libstdc++-v3/src/.libs -B/usr/local/alpha-dec-osf4.0g/bin/ -B/usr/local/alpha-dec-osf4.0g/lib/ -isystem /usr/local/alpha-dec-osf4.0g/include -nostdinc++ -I/usr2/sys/usr/local/src/bld311/alpha-dec-osf4.0g/libstdc++-v3/include/alpha-dec-osf4.0g -I/usr2/sys/usr/local/src/bld311/alpha-dec-osf4.0g/libstdc++-v3/include -I../../../../gcc-3.1.1/libstdc++-v3/libsupc++ -I../../../../gcc-3.1.1/libstdc++-v3/libmath -g -O2 -mieee -fno-implicit-templates -Wall -Wno-format -W -Wwrite-strings -Winline -fdiagnostics-show-location=once -g -c ../../../../gcc-3.1.1/libstdc++-v3/src/locale-inst.cc -DPIC -o .libs/locale-inst.o >How-To-Repeat: unpack gcc-3.1.1-tar.gz mkdir bld311 cd bld311 ../gcc-3.1.1/configure --with-stabs --enable-languages=c,c++,f77,java make >Fix: My fix was to build decl.o explicitely using the same command as make but w/ -O instead of -O2. To build locale-inst.o, I had to edit the appropriate makefile to force -O instead of -O2 to be used. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-08-09 14:06 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=200208091404.JAA24932@baobab.cs.uwplatt.edu \ --to=hasker@baobab.cs.uwplatt.edu \ --cc=gcc-gnats@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).