public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joe Hughes" <jhughesjr@comcast.net>
To: gcc-help@gcc.gnu.org
Subject: Bootstrap comparison failure cp/tree.o differs 3.4.1
Date: Tue, 20 Jul 2004 13:13:00 -0000	[thread overview]
Message-ID: <40FD1A87.1040803@comcast.net> (raw)

Hello,
Having issues building 3.4.1, received this error comparing stage2 and
stage3 :

case "gnucompare" in *compare | *compare-lean ) stage=2 ;; * )
stage=`echo gnucompare | sed -e 's,^[a-z]*compare\([0-9][0-9]*\).*,\1,'`
;; esac; \
for dir in . cp f java objc; do \
   if [ "`echo $dir/*.o`" != "$dir/*.o" ] ; then \
     for file in $dir/*.o; do \
       case "gnucompare" in \
         slowcompare* ) \
           tail +16c ./$file > tmp-foo1; \
           tail +16c stage$stage/$file > tmp-foo2 \
             && (cmp tmp-foo1 tmp-foo2 > /dev/null 2>&1 || echo $file
differs >> .bad_compare) || true; \
           ;; \
         fastcompare* ) \
           cmp $file stage$stage/$file 16 16 > /dev/null 2>&1; \
           test $? -eq 1 && echo $file differs >> .bad_compare || true; \
           ;; \
         gnucompare* ) \
           cmp --ignore-initial=16 $file stage$stage/$file > /dev/null
2>&1; \
           test $? -eq 1 && echo $file differs >> .bad_compare || true; \
           ;; \
       esac ; \
     done; \
   else true; fi; \
done
rm -f tmp-foo*
case "gnucompare" in *compare | *compare-lean ) stage=2 ;; * )
stage=`echo gnucompare | sed -e 's,^[a-z]*compare\([0-9][0-9]*\).*,\1,'`
;; esac; \
if [ -f .bad_compare ]; then \
   echo "Bootstrap comparison failure!"; \
   cat .bad_compare; \
   exit 1; \
else \
   case "gnucompare" in \
     *-lean ) rm -rf stage$stage ;; \
     *) ;; \
   esac; true; \
fi
Bootstrap comparison failure!
cp/tree.o differs


Anyone have any suggestions?

Thanks in advance.

Cheers,
Joe


                 reply	other threads:[~2004-07-20 13:13 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=40FD1A87.1040803@comcast.net \
    --to=jhughesjr@comcast.net \
    --cc=gcc-help@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).