public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christian Jönsson <chj@j-son.org>
To: gcc <gcc@gcc.gnu.org>
Subject: stage1 bootstrap failuer to build gcc.3.3: cppfiles.c:1168: error: parse error before ']' token etc.
Date: Sun, 18 Aug 2002 07:42:00 -0000	[thread overview]
Message-ID: <20020818144150.GA2411@j-son.org> (raw)

I'm trying to build gcc-3.3 (2002-08-18 cvs) but get this error


stage1/xgcc -Bstage1/ -B/usr/sparc-linux/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. -I/opt/gcc+binutils/gcc/gcc -I/opt/gcc+binutils/gcc/gcc/. -I/opt/gcc+binutils/gcc/gcc/config -I/opt/gcc+binutils/gcc/gcc/../include /opt/gcc+binutils/gcc/gcc/cppfiles.c -o cppfiles.o
stage1/xgcc -Bstage1/ -B/usr/sparc-linux/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. -I/opt/gcc+binutils/gcc/gcc -I/opt/gcc+binutils/gcc/gcc/. -I/opt/gcc+binutils/gcc/gcc/config -I/opt/gcc+binutils/gcc/gcc/../include /opt/gcc+binutils/gcc/gcc/cpptrad.c -o cpptrad.o
stage1/xgcc -Bstage1/ -B/usr/sparc-linux/bin/ -c   -g -O2 -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long   -DHAVE_CONFIG_H    -I. -I. -I/opt/gcc+binutils/gcc/gcc -I/opt/gcc+binutils/gcc/gcc/. -I/opt/gcc+binutils/gcc/gcc/config -I/opt/gcc+binutils/gcc/gcc/../include /opt/gcc+binutils/gcc/gcc/cpphash.c -o cpphash.o
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1168: error: parse error before ']' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1380: error: syntax error at '#' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1385: error: syntax error at '#' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1385: error: syntax error at '#' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1388: error: syntax error at '#' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1388: error: syntax error at '#' token
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1451:21: warning: null character(s) ignored
/opt/gcc+binutils/gcc/gcc/cppfiles.c:1451: confused by earlier errors, bailing out
make[2]: *** [cppfiles.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/opt/gcc+binutils/objdir/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/opt/gcc+binutils/objdir/gcc'
make: *** [bootstrap-lean] Error 2

Any idea of what might be going wrong for me?

This was on a Debian 3.0 (Woody) quad ROSS sun4m system with these
packages:

binutils                           2.12.90.0.1-4
dejagnu                            1.4.2-1.1
gcc                                2:2.95.4-14 (Debian prerelease)
gcc-2.95			   1:2.95.4-7 (Debian prerelease)
gnat				   3.14p-3
self compiled 2.4.19-rc3 SMP kernel running during build and test

In-tree joined gcc and binutils cvs trunks.

             reply	other threads:[~2002-08-18  7:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-18  7:42 Christian Jönsson [this message]
2002-08-18  7:53 ` Christian Jönsson
     [not found] ` <000b01c246c7$368d95c0$0301a8c0@D90V2D0J>
2002-08-21  7:03   ` Christian Jönsson
2002-08-27  9:33     ` Christian Jönsson
2002-08-27  9:57       ` Neil Booth
2002-09-01  8:29         ` Christian Jönsson
2002-09-03 12:54         ` Neil Booth
2002-09-04 11:57           ` Christian Jönsson
2002-09-04 12:44             ` 'Neil Booth'
2002-09-05 11:01               ` Zack Weinberg
2002-09-05 11:05                 ` 'Neil Booth'
2002-09-10 16:56                   ` Zack Weinberg
2002-09-10 23:42                     ` 'Neil Booth'
2002-09-11 13:18                       ` Zack Weinberg
2002-09-11 14:32                         ` 'Neil Booth'
2002-09-11 16:02                           ` Zack Weinberg
2002-09-12  1:05                             ` 'Neil Booth'
2002-09-18 14:18                               ` Zack Weinberg
2002-09-22 14:00                               ` Christian Jönsson
2002-10-04 13:14                                 ` Neil Booth

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=20020818144150.GA2411@j-son.org \
    --to=chj@j-son.org \
    --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).