public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lee, Michael, Superior Court" <mlee2@co.alameda.ca.us>
To: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: FW: error making gcc on HP-UX 11.00
Date: Wed, 01 Aug 2001 07:10:00 -0000	[thread overview]
Message-ID: <0957DC44897FD41197BE00A0C9E52418F2BBD7@ALCOEX08> (raw)

Ok.  I followed the steps 1 - 7 below and everything seemed to work OK.
Then I did a "make bootstrap-lean" to make gcc and wound up with the
following errors:

make[1]: *** [compare-lean] Error 1
make[1]: Leaving directory `/forte/ffx/gccObject/gcc'
make: *** [bootstrap-lean] Error 2

Thanks for your help.

-----Original Message-----
From: ERICSON,MATHEW (A-Australia,ex1)
[ mailto:mathew_ericson@agilent.com ]
Sent: Tuesday, July 31, 2001 3:19 PM
To: 'Lee, Michael, Superior Court'; 'gcc-help@gcc.gnu.org'
Subject: RE: error making gcc on HP-UX 11.00


Michael,

I had this error when I was not using GNU make 3.79.1.
Essentially if you are building with the free compiler that comes with HP-UX
I find this is the best case

1. export PATH=/usr/bin (to only pick up /usr/bin/cc)
2. build make-3.79.1
3. export PATH=/path/to/GNUmake:/usr/bin (so you now use GNU make)
4. build binutils-2.11.2
5. export PATH=/path/to/binutils:/path/to/GNUmake:/usr/bin (so you use the
GNU as)
6. cd objdir
7. configure --prefix=/opt/gcc-3.0 ..etc...etc.

mathew


-----Original Message-----
From: Lee, Michael, Superior Court [ mailto:mlee2@co.alameda.ca.us ]
Sent: Wednesday, August 01, 2001 2:39 AM
To: 'gcc-help@gcc.gnu.org'
Subject: error making gcc on HP-UX 11.00


I got the following error part way through running make bootstrap-lean:

(Bundled) cc: warning 480: The -g option is available only with the C/ANSI C
pro
duct; ignored.
/usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (genflags.o) was
dete
cted. The linked output may not run on a PA 1.x system.
        ./genflags /forte/ffx/gcc-3.0/gcc/config/pa/pa.md > tmp-flags.h
        /bin/sh /forte/ffx/gcc-3.0/gcc/move-if-change tmp-flags.h
insn-flags.h
        echo timestamp > s-flags
        (cd /forte/ffx/gcc-3.0/gcc && false  -o c-p$$.c c-parse.y && \
        mv -f c-p$$.c c-parse.c)
*** Error exit code 1
 
Stop.
*** Error exit code 1
 
Stop.
*** Error exit code 1
 
Stop.


Does anyone one know what this means, or where I can look for a more
descriptive message?

Thanks.

             reply	other threads:[~2001-08-01  7:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01  7:10 Lee, Michael, Superior Court [this message]
2001-08-01 10:46 ` Alexandre Oliva
2001-08-03 10:05 Lee, Michael, Superior Court
2001-08-03 12:25 ` Alexandre Oliva
2001-08-03 12:53   ` law

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=0957DC44897FD41197BE00A0C9E52418F2BBD7@ALCOEX08 \
    --to=mlee2@co.alameda.ca.us \
    --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).