public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: neil@daikokuya.co.uk
Cc: gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Subject: New bootstrap failure on sparc-solaris2.7, fails to define "sparc"
Date: Sun, 18 May 2003 16:19:00 -0000	[thread overview]
Message-ID: <200305181610.MAA06882@caip.rutgers.edu> (raw)

Neil,

I'm getting a new bootstrap failure on sparc-sun-solaris2.7 within the
last day or so., probably related to recent changes you made.  It dies
in stage1 building any libgcc target file.  E.g.

 > /teal/tmpdisk/ghazi/gcc-testing/34/build/gcc/xgcc
 > -B/teal/tmpdisk/ghazi/gcc-testing/34/build/gcc/
 > -B/usr/local/sparc-sun-solaris2.7/bin/
 > -B/usr/local/sparc-sun-solaris2.7/lib/ -isystem
 > /usr/local/sparc-sun-solaris2.7/include -isystem
 > /usr/local/sparc-sun-solaris2.7/sys-include -DIN_GCC -W -Wall
 > -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem
 > ./include -I. -I. -I../../egcc-CVS20030518/gcc
 > -I../../egcc-CVS20030518/gcc/. -I../../egcc-CVS20030518/gcc/config
 > -I../../egcc-CVS20030518/gcc/../include \
 > -c ../../egcc-CVS20030518/gcc/config/sparc/gmon-sol2.c -o gmon.o
 > 
 > In file included from /usr/include/sys/feature_tests.h:15,
 >                  from /teal/tmpdisk/ghazi/gcc-testing/34/build/gcc/include/stdio.h:36,
 >                  from ../../egcc-CVS20030518/gcc/tsystem.h:71,
 >                  from ../../egcc-CVS20030518/gcc/config/sparc/gmon-sol2.c:36:
 > /usr/include/sys/isa_defs.h:322:2: #error "ISA not supported"
 > In file included from /teal/tmpdisk/ghazi/gcc-testing/34/build/gcc/include/limits.h:11,
 >                  from ../../egcc-CVS20030518/gcc/tsystem.h:89,
 >                  from ../../egcc-CVS20030518/gcc/config/sparc/gmon-sol2.c:36:
 > /teal/tmpdisk/ghazi/gcc-testing/34/build/gcc/include/syslimits.h:64:2: #error "chars are signed or unsigned"
 > make[2]: *** [gmon.o] Error 1

The problem appears to be that neither "sparc" nor "__sparc" gets
defined.  (If I add -Dsparc or -D__sparc to the above invocation, the
compilation succeeds.)

Would you please take a look?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu

             reply	other threads:[~2003-05-18 16:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-18 16:19 Kaveh R. Ghazi [this message]
2003-05-18 19:34 ` Neil Booth
2003-05-18 20:03 ` Neil Booth
2003-05-18 20:57   ` Paolo Carlini
2003-05-19  3:39   ` Kaveh R. Ghazi
2003-05-19  5:37     ` 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=200305181610.MAA06882@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=neil@daikokuya.co.uk \
    /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).