public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Manfred Hollstein <manfred@s-direktnet.de>
To: robertl@dgii.com
Cc: egcs@cygnus.com
Subject: Re: int compiler error bootstrapping on openserver
Date: Sat, 11 Apr 1998 04:07:00 -0000	[thread overview]
Message-ID: <13615.4477.425130.574673@saturn.s-direktnet.de> (raw)
In-Reply-To: <19980410184543.56599@dgii.com>

On Fri, 10 April 1998, 18:45:43, robertl@dgii.com wrote:

 > OpenServer worked pretty well oh, about three days ago.  I just did
 > an update (and did another since seeing this just in case things were
 > wierded out temporarily) and a make.  I did another make just to be sure
 > this wasn't a fleeting (RAM error) problem.   It seems repeatable.
 > 
 > host==target==i486-pc-sco3.2v5.0.4
 > 
 > The make proceeds OK until we get to:
 > 
 > /home/play/negcs/gcc/xgcc -B/home/play/negcs/gcc/ -O2   -DIN_GCC    -g -O2 -Wall  -I./include   -g1  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -fexceptions    -I. -I../../egcs/gcc -I../../egcs/gcc/config \
 >   -c ../../egcs/gcc/cp/tinfo.cc
 > ../../egcs/gcc/cp/tinfo.cc: In method `void * __class_type_info::dcast(const class type_info &, int, void *, const class type_info * = 0, void * = 0) const':
 > ../../egcs/gcc/cp/tinfo.cc:80: warning: comparison between signed and unsigned
 > include/typeinfo: At top level:
 > include/typeinfo:64: Internal compiler error.
 > include/typeinfo:64: Please submit a full bug report to `egcs-bugs@cygnus.com'.
 > make[4]: *** [tinfo.o] Error 1
 > make[3]: *** [libgcc2.a] Error 1
 > make[2]: *** [stmp-multilib-sub] Error 2
 > make[1]: *** [stmp-multilib] Error 1
 > make: *** [all-gcc] Error 2
 > 
 > I just did a 'cvs update' and resovled even the generated files
 > (configure, parse,etc.) against those in the tree and still get the
 > same.
 > 
 > I know we've seen some ICE's while building tinfo.cc before in quarters
 > past, but I really can't recall the details.
 > 
 > This isn't during the coff build, so it should be pretty close to the same
 > thing the linux crowd would be doing.    Are you guys seeing that fail?

Yep, same here on i586-linux-gnulibc1.

manfred

  reply	other threads:[~1998-04-11  4:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-10 20:10 Robert Lipe
1998-04-11  4:07 ` Manfred Hollstein [this message]
1998-04-11  4:07 ` Jean-Pierre Radley
1998-04-11  6:15 ` int compiler error bootstrapping on openserver [also onm68k-next-nextstep3] Toon Moene

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=13615.4477.425130.574673@saturn.s-direktnet.de \
    --to=manfred@s-direktnet.de \
    --cc=egcs@cygnus.com \
    --cc=robertl@dgii.com \
    /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).