public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gypsy@Media.mit.edu
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/7509: gcc 3.1.1 bootstrap fails in stage2
Date: Tue, 06 Aug 2002 10:46:00 -0000	[thread overview]
Message-ID: <20020806174335.6691.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]


>Number:         7509
>Category:       bootstrap
>Synopsis:       gcc 3.1.1 bootstrap fails in stage2
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 06 10:46:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     gypsy@Media.mit.edu
>Release:        gcc-3.1.1 thread mode single
>Organization:
>Environment:
Compaq XP1000, AlphaEV6, Tru64 5.0A (alphaev6-dec-osf5.0A)
>Description:
The comand is:  CC=cc CFLAGS="-I/usr/local/lib" /usr/local/gcc-3.1.1/configure

The CFLAGS are necessary for linking against GNU libiconv.so 1.8, which otherwise would conflict with Tru64's own libiconv.so.

The result is:



stage2/xgcc -Bstage2/ -B/usr/local/alphaev6-dec-osf5.0/bin/ -c -DIN_GCC    -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long  -DHAVE_CONFIG_H    -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../include ../../gcc/predict.c -o predict.o
../../gcc/predict.c: In function `propagate_freq':
../../gcc/predict.c:708: Internal compiler error in @œ
                                                      @, at F:537413072
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
gmake[2]: *** [predict.o] Error 1
gmake[2]: Leaving directory `/usr/local/src/gcc-3.1.1/obj/gcc'
gmake[1]: *** [stage3_build] Error 2
gmake[1]: Leaving directory `/usr/local/src/gcc-3.1.1/obj/gcc'
gmake: *** [bootstrap] Error 2
bash-2.05a# 

It might be helpful to know that this works on an alphaev56-dec-osf4.0f system.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2002-08-06 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 10:46 gypsy [this message]
2002-12-05 13:32 bangerth

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=20020806174335.6691.qmail@sources.redhat.com \
    --to=gypsy@media.mit.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: 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).