public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ralf.hildebrandt@charite.de
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/7141: GCC-3.1 does not build on DEC OSF1 4.0e
Date: Thu, 27 Jun 2002 00:36:00 -0000	[thread overview]
Message-ID: <20020627064934.11089.qmail@sources.redhat.com> (raw)


>Number:         7141
>Category:       bootstrap
>Synopsis:       GCC-3.1 does not build on DEC OSF1 4.0e
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jun 26 23:56:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ralf.hildebrandt@charite.de
>Release:        unknown-1.0
>Organization:
>Environment:
OSF1 mailhost.charite.de V4.0 1091 alpha
# gcc -v
Reading specs from /usr/local/lib/gcc-lib/alpha-dec-osf4.0e/2.95.3/specs
gcc version 2.95.3 20010315 (release)
# /usr/local/bin/make --version
GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
Built for alpha-dec-osf4.0e
# bison --version
bison (GNU Bison) 1.35
>Description:
../configure --host=alpha-dec-osf4.0e --enable-shared --enable-version-specific-runtime-libs
Then, after "make bootstrap-lean" I got:

test -d po || mkdir po
: --statistics -o po/tr.gmo ../../gcc/po/tr.po
stage1/xgcc -Bstage1/ -B/usr/local/alpha-dec-osf4.0e/bin/ -DIN_GCC     -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  -o cc1  c-parse.o c-lang.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o  c-convert.o c-aux-info.o c-common.o c-format.o c-semantics.o  c-objc-common.o libcpp.a  main.o libbackend.a ./intl/libintl.a  -liconv  ../libiberty/libiberty.a
stage1/xgcc -Bstage1/ -B/usr/local/alpha-dec-osf4.0e/bin/ -DIN_GCC     -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  -o tradcpp0  tradcpp.o tradcif.o mkdeps.o cppdefault.o version.o intl.o ./intl/libintl.a  -liconv  ../libiberty/libiberty.a
stage1/xgcc -Bstage1/ -B/usr/local/alpha-dec-osf4.0e/bin/ -DIN_GCC     -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H  gcov.o intl.o version.o ./intl/libintl.a  -liconv  ../libiberty/libiberty.a -o gcov
stage1/xgcc -Bstage1/ -B/usr/local/alpha-dec-osf4.0e/bin/ -c -DIN_GCC     -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes   -DHAVE_CONFIG_H    -I. -Icp -I../../gcc -I../../gcc/cp  -I../../gcc/config -I../../gcc/../include ../../gcc/cp/decl.c -o cp/decl.o
virtual memory exhausted: Not enough space
*** Exit 1
Stop.
*** Exit 1
Stop.
*** Exit 1
Stop.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-06-27  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-27  0:36 ralf.hildebrandt [this message]
2003-05-14 18:56 Dara Hazeghi
2003-05-17  6:51 giovannibajo

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=20020627064934.11089.qmail@sources.redhat.com \
    --to=ralf.hildebrandt@charite.de \
    --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: 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).