public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jss@ast.cam.ac.uk
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10169: Bootstrap fails on mainline with Tru64 5.1B
Date: Thu, 20 Mar 2003 17:56:00 -0000	[thread overview]
Message-ID: <20030320175246.31906.qmail@sources.redhat.com> (raw)


>Number:         10169
>Category:       bootstrap
>Synopsis:       Bootstrap fails on mainline with Tru64 5.1B
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 20 17:56:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     jss@ast.cam.ac.uk
>Release:        2003-03-20 mainline
>Organization:
>Environment:
Tru64 5.1B, using cc as bootstrap compiler.
>Description:
../gcc/gcc/configure --enable-languages=c,c++,f77

stage1/xgcc -Bstage1/ -B/usr/local/alphaev6-dec-osf5.1/bin/   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -Werror -fno-common   -DHAVE_CONFIG_H  -o f771 f/bad.o f/bit.o f/bld.o f/com.o f/data.o f/equiv.o f/expr.o f/global.o f/implic.o f/info.o f/intrin.o f/lab.o f/lex.o f/malloc.o f/name.o f/parse.o f/src.o f/st.o f/sta.o f/stb.o f/stc.o f/std.o f/ste.o f/storag.o f/stp.o f/str.o f/sts.o f/stt.o f/stu.o f/stv.o f/stw.o f/symbol.o f/target.o f/top.o f/type.o f/where.o main.o libbackend.a ./intl/libintl.a  -liconv  ../libiberty/libiberty.a
stage1/xgcc -Bstage1/ -B/usr/local/alphaev6-dec-osf5.1/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -Werror -fno-common   -DHAVE_CONFIG_H    -I. -I. -I../../gcc/gcc/gcc -I../../gcc/gcc/gcc/. -I../../gcc/gcc/gcc/config -I../../gcc/gcc/gcc/../include ../../gcc/gcc/gcc/mips-tfile.c -o mips-tfile.o
../../gcc/gcc/gcc/mips-tfile.c:1134: warning: missing initializer
../../gcc/gcc/gcc/mips-tfile.c:1134: warning: (near initialization for `init_file.fdr.reserved2')
../../gcc/gcc/gcc/mips-tfile.c: In function `main':
../../gcc/gcc/gcc/mips-tfile.c:4861: warning: implicit declaration of function `getopt'
make[2]: *** [mips-tfile.o] Error 1
make[2]: Leaving directory `/tmp_mnt/scratch/jss/builds/gcc-out/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/tmp_mnt/scratch/jss/builds/gcc-out/gcc'
make: *** [bootstrap] Error 2

The missing initialiser looks like an extra comma to me (in the alpha specific part of the file).
Presumably there's also a missing include for getopt too.
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2003-03-20 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-20 17:56 jss [this message]
2003-05-14 18:16 Dara Hazeghi
2003-05-14 18:36 Roger Sayle
2003-05-15 17:16 Jeremy Sanders
2003-05-16 16:46 Jeremy Sanders

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=20030320175246.31906.qmail@sources.redhat.com \
    --to=jss@ast.cam.ac.uk \
    --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).