public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: llewelly@xmission.com
To: "Foster, Paul" <Paul.Foster@hey.nhs.uk>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: Please help
Date: Fri, 02 Jul 2004 20:01:00 -0000	[thread overview]
Message-ID: <s3roemygovt.fsf@solaris.xmission.com> (raw)
In-Reply-To: <1FFF61B8F8A0364B950E074FB6B9E8B9E84992@rhhtexchange.hey.nhs.uk>

"Foster, Paul" <Paul.Foster@hey.nhs.uk> writes:

> When building Gcc with the make bootstrap command on a hp-ux system
> with version 10.20, after a few minutes I get the following see
> attachment.

Please see http://gcc.gnu.org/install/specific.html#hppa*-hp-hpux10
>  
> I think they are comparison error between stage 1 and stage 2?

Yes:

#    The HP assembler on these systems has some problems. Most notably the
#    nassembler inserts timestamps into each object file it creates, causing
#    the 3-stage comparison test to fail during a make bootstrap.
#    You should be able to continue by saying make all after getting the
#    failure from make bootstrap.

(from the above link)

  reply	other threads:[~2004-07-02 20:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 15:34 Foster, Paul
2004-07-02 20:01 ` llewelly [this message]
     [not found] <20021219155354.82824.qmail@web12207.mail.yahoo.com>
2002-12-20 20:45 ` please help LLeweLLyn Reese
     [not found] <616BE6A276E3714788D2AC35C40CD18D981986@whale.softwire.co.uk>
2002-12-18  4:44 ` Rupert Wood
2002-12-18  6:33   ` Deva Seetharam
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18  2:46 Ashwin Varma
2002-12-18 12:44 ` LLeweLLyn Reese
2002-03-15 12:30 Please help Subhash Agrawal
2001-09-24 23:28 Please Help Matthew Price
2001-09-28 17:33 ` Alexandre Oliva
2000-11-06  0:03 please help Ooi EnYee
2000-11-06  0:36 ` Anthony Lee

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=s3roemygovt.fsf@solaris.xmission.com \
    --to=llewelly@xmission.com \
    --cc=Paul.Foster@hey.nhs.uk \
    --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).