public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: V.Haisman@sh.cvut.cz
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/6400: problem compiling gcc/crtstuff.c during bootstrap
Date: Sun, 21 Apr 2002 15:26:00 -0000 [thread overview]
Message-ID: <20020421222318.15247.qmail@sources.redhat.com> (raw)
>Number: 6400
>Category: bootstrap
>Synopsis: problem compiling gcc/crtstuff.c during bootstrap
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Apr 21 15:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: V.Haisman@sh.cvut.cz
>Release: 3.1
>Organization:
>Environment:
>Description:
I have problem compiling GCC 3.1 from CVS. It is unable to compile gcc/crtstuff.c. I get loads of errors about non-ascii chars and some other errors. Error log file has about 1.4MB. These are first few lines:
make[1]: Entering directory `/home/4/wilx/tmp/gcc31/objdir/libiberty'
make[2]: Entering directory `/home/4/wilx/tmp/gcc31/objdir/libiberty/testsuite'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/4/wilx/tmp/gcc31/objdir/libiberty/testsuite'
make[1]: Leaving directory `/home/4/wilx/tmp/gcc31/objdir/libiberty'
Bootstrapping the compiler
make[1]: Entering directory `/home/4/wilx/tmp/gcc31/objdir/gcc'
make CC="gcc" libdir=/home/4/wilx/lib LANGUAGES="c " \
CFLAGS="-g " MAKEINFO="makeinfo " \
MAKEINFOFLAGS=""
make[2]: Entering directory `/home/4/wilx/tmp/gcc31/objdir/gcc'
(cd intl && make all)
make[3]: Entering directory `/home/4/wilx/tmp/gcc31/objdir/gcc/intl'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/home/4/wilx/tmp/gcc31/objdir/gcc/intl'
./xgcc -B./ -B/home/4/wilx/i386-unknown-freebsd3.5/bin/ -isystem /home/4/wilx/i386-unknown-freebsd3.5/include -isystem /home/4/wilx/i386-unknown-freebsd3.5/s
ys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -I. -I. -I../../srcdir/gcc -I../../srcdir/gc
c/. -I../../srcdir/gcc/config -I../../srcdir/gcc/../include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions \
-c ../../srcdir/gcc/crtstuff.c -DCRT_BEGIN \
-o crtbegin.o
../../srcdir/gcc/crtstuff.c:613: parse error before numeric constant
../../srcdir/gcc/crtstuff.c:615: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:617: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:619: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:621: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:622: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:624: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:626: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:628: invalid suffix on integer constant
../../srcdir/gcc/crtstuff.c:628: warning: type defaults to `int' in declaration of `Wed'
../../srcdir/gcc/crtstuff.c:628: parse error before numeric constant
../../srcdir/gcc/crtstuff.c:629: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:630: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:630: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:631: warning: type defaults to `int' in declaration of `Wed'
../../srcdir/gcc/crtstuff.c:631: parse error before numeric constant
../../srcdir/gcc/crtstuff.c:632: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:633: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:634: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:634: too many decimal points in floating constant
../../srcdir/gcc/crtstuff.c:635: warning: type defaults to `int' in declaration of `Wed'
../../srcdir/gcc/crtstuff.c:635: parse error before numeric constant
../../srcdir/gcc/crtstuff.c:636: invalid suffix on floating constant
../../srcdir/gcc/crtstuff.c:636: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:638: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:640: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:640: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:641: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:641: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:641: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:641: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:642: syntax error at '@' token
../../srcdir/gcc/crtstuff.c:644: warning: type defaults to `int' in declaration of `charset'
../../srcdir/gcc/crtstuff.c:644: `us' undeclared here (not in a function)
../../srcdir/gcc/crtstuff.c:645: `ascii' undeclared here (not in a function)
../../srcdir/gcc/crtstuff.c:645: parse error before "Content"
../../srcdir/gcc/crtstuff.c:645: invalid suffix on integer constant
../../srcdir/gcc/crtstuff.c:652:7: missing terminating ' character
../../srcdir/gcc/crtstuff.c:652:7: warning: character constant too long
../../srcdir/gcc/crtstuff.c:658:8: missing terminating ' character
../../srcdir/gcc/crtstuff.c:658:8: warning: character constant too long
When I try to run the command with addition of -save-temps parameter I get this:
./xgcc -B./ -B/home/4/wilx/i386-unknown-freebsd3.5/bin/ -isystem /home/4/wilx/i386-unknown-freebsd3.5/include -isystem /home/4/wilx/i386-unknown-freebsd3.5/sys-include -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include -I. -I. -I../../srcdir/gcc -I../../srcdir/gcc/. -I../../srcdir/gcc/config -I../../srcdir/gcc/../include -g0 -finhibit-size-directive -fno-inline-functions -fno-exceptions -save-temps -c ../../srcdir/gcc/crtstuff.c -DCRT_BEGIN -o crtbegin.o
../../srcdir/gcc/crtstuff.c:652:7: missing terminating ' character
../../srcdir/gcc/crtstuff.c:658:8: missing terminating ' character
../../srcdir/gcc/crtstuff.c:659:11: missing terminating ' character
../../srcdir/gcc/crtstuff.c:661:2: missing terminating ' character
../../srcdir/gcc/crtstuff.c:662:69: missing terminating ' character
../../srcdir/gcc/crtstuff.c:663:58: missing terminating ' character
../../srcdir/gcc/crtstuff.c:1253:1: warning: null character(s) ignored
../../srcdir/gcc/crtstuff.c:3106:1: warning: "FUNCTION_PROFILER" redefined
In file included from tconfig.h:23,
from ../../srcdir/gcc/crtstuff.c:61:
../../srcdir/gcc/config/i386/freebsd.h:52:1: warning: this is the location of the previous definition
../../srcdir/gcc/crtstuff.c:4157:1: warning: "DBX_REGISTER_NUMBER" redefined
../../srcdir/gcc/config/i386/freebsd.h:43:1: warning: this is the location of the previous definition
../../srcdir/gcc/crtstuff.c:4552:1: warning: null character(s) ignored
../../srcdir/gcc/crtstuff.c:5322:1: warning: null character(s) ignored
xgcc: Internal error: Segmentation fault (program cpp0)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
These are configuration flags I have used. The machine is FreeBSD 3.5, bootstraping compiler used is gcc-2.95.2.
logout ~/tmp/gcc31/objdir/gcc>./xgcc -v
Using built-in specs.
Configured with: ../srcdir/configure --prefix=/home/4/wilx --enable-threads=posix --enable-version-specific-runtime-libs --enable-languages=c,c++,gcov --enable-nls : (reconfigured) ../srcdir/configure --prefix=/home/4/wilx --enable-threads=posix --enable-version-specific-runtime-libs --enable-languages=c,c++,gcov --disable-nls
Thread model: posix
gcc version 3.1 20020420 (prerelease)
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2002-04-21 22:26 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=20020421222318.15247.qmail@sources.redhat.com \
--to=v.haisman@sh.cvut.cz \
--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).