From: "Dennis I. Chernoivanov" <cdi@sparc.spb.su>
To: gcc@gcc.gnu.org
Subject: Re: egcs-20000313 on Solaris
Date: Wed, 15 Mar 2000 07:27:00 -0000 [thread overview]
Message-ID: <20000315182506.A19491@sparc.spb.su> (raw)
In-Reply-To: <Pine.GSO.4.05.10003151008010.290-100000@alina.acomp.usf.edu>
Same for me. Shouldn't it be "rli->record_align" on line 691 ?
Regards,
--Dennis
On Wed, Mar 15, 2000 at 10:11:36AM -0500, James Black wrote:
> Hello,
> The latest snapshot failed to build on my machine. Here is the system
> info and the errors.
>
> ../../egcs-20000313/gcc/stor-layout.c: In function `finalize_record_size':
> ../../egcs-20000313/gcc/stor-layout.c:691: `record_align' undeclared
> (first use in this function)
> ../../egcs-20000313/gcc/stor-layout.c:691: (Each undeclared identifier is
> reported only once
> ../../egcs-20000313/gcc/stor-layout.c:691: for each function it appears
> in.)
> make[1]: *** [stor-layout.o] Error 1
> ../../egcs-20000313/gcc/genoutput.c: In function `scan_operands':
> ../../egcs-20000313/gcc/genoutput.c:444: warning: passing arg 1 of
> `strip_whitespace' discards qualifiers from pointer target type
> ../../egcs-20000313/gcc/genoutput.c:472: warning: passing arg 1 of
> `strip_whitespace' discards qualifiers from pointer target type
> make[1]: *** No rule to make target `stor-layout.o', needed by
> `stamp-objlist'.
> make[1]: *** No rule to make target `stamp-objlist', needed by `cc1plus'.
> make[1]: *** No rule to make target `cc1', needed by `s-under'.
> make[1]: *** No rule to make target `xsys-protos.h', needed by
> `fix-header'.
> make[1]: *** No rule to make target `stmp-fixproto', needed by
> `libgcc2.ready'.
> make[1]: *** No rule to make target `underscore.o', needed by `c++filt'.
> make[1]: Target `all' not remade because of errors.
> `
>
> SunOS alina 5.6 Generic_105181-14 sun4u sparc SUNW,Ultra-1
> gcc version 2.96 20000221 (experimental)
>
> ../egcs-20000313/configure
> --with-gcc-version-trigger=/home1/egcs/egcs-20000313/gcc/version.c
> --host=sparc-sun-solaris2.6 --prefix=/usr/local/egcs/
> --enable-haifa --with-gnu-as --with-gnu-ld --enable-threads
> --with-cpu=ultrasparc --enable-version-specific-runtime-libs
>
> This was the same options I used to build the version I am currently
> using.
>
> --
> ========================================================================
> James Black (Elec Eng Graduate student)
> e-mail: jblack@ieee.org http://www.eng.usf.edu/~black/index.html
> For my public key: finger -l black@eng.usf.edu
> "Class is an aura of confidence that is being sure without being
> cocky. Class has nothing to do with money. Class never runs scared.
> It is self-discipline and self-knowledge. It's the sure-footedness that
> comes with having proved you can meet life."
> ~ Ann Landers ~
> ************************************************************************
--
Regards,
--Dennis
next prev parent reply other threads:[~2000-03-15 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 7:15 James Black
2000-03-15 7:27 ` Dennis I. Chernoivanov [this message]
2000-03-15 7:46 'David Scott Urban
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=20000315182506.A19491@sparc.spb.su \
--to=cdi@sparc.spb.su \
--cc=gcc@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).