From: Toon Moene <toon@moene.indiv.nluug.nl>
To: egcs@cygnus.com
Subject: Results for egcs-971207 on m68k-next-nextstep3
Date: Wed, 10 Dec 1997 07:08:00 -0000 [thread overview]
Message-ID: <9712101506.AA20265@moene.indiv.nluug.nl> (raw)
First of all, the following completed perfectly:
cd objdir
make all-texinfo all-bison all-byacc all-binutils all-gas all-ld
cd gcc
make bootstrap
make install-headers-tar
cd ..
make bootstrap3
[ I need this strange bootstrap procedure because of the header
file curiosity in NEXTSTEP ]
However, I got several warnings during the build:
stage1/xgcc -Bstage1/ -c -DIN_GCC -O2 -g -DHAVE_CONFIG_H
-I. -I. -I./config cplus-dem.c
In file included from demangle.h:24,
from cplus-dem.c:35:
gansidecl.h:81: warning: `bcopy' redefined
/NextDeveloper/Headers/ansi/string.h:119: warning: this is the
location of the previous definition
gansidecl.h:85: warning: `bzero' redefined
/NextDeveloper/Headers/ansi/string.h:125: warning: this is the
location of the previous definition
gansidecl.h:89: warning: `bcmp' redefined
/NextDeveloper/Headers/ansi/string.h:122: warning: this is the
location of the previous definition
gansidecl.h:93: warning: `rindex' redefined
/NextDeveloper/Headers/ansi/string.h:116: warning: this is the
location of the previous definition
gansidecl.h:97: warning: `index' redefined
/NextDeveloper/Headers/ansi/string.h:112: warning: this is the
location of the previous definition
and:
ranlib: same symbol defined in more than one member in: tmplibgcc.a
(table of contents will not be sorted)
ranlib: file: tmplibgcc.a(_floatditf.o) defines symbol:
__GLOBAL_$F$._libgcc2.c
ranlib: file: tmplibgcc.a(_fixunstfdi.o) defines symbol:
__GLOBAL_$F$._libgcc2.c
ranlib: file: tmplibgcc.a(_ctors.o) defines symbol:
__GLOBAL_$F$._libgcc2.c
ranlib: file: tmplibgcc.a(_fixtfdi.o) defines symbol:
__GLOBAL_$F$._libgcc2.c
ranlib: file: tmplibgcc.a(_shtab.o) defines symbol:
__GLOBAL_$F$._libgcc2.c
also interesting is:
filebuf.cc: In method `class filebuf * filebuf::open(const char *,
int, int = 436)':
filebuf.cc:114: warning: implicit declaration of function `int open(...)'
and:
stdiostream.cc: In method `long int stdiobuf::sys_read(char *, long
int)':
stdiostream.cc:77: warning: ANSI C++ forbids declaration `ch' with
no type
However, what did me in was the following:
% cat dimstar.f
subroutine star(aap, noot)
dimension aap(*)
end
% /usr/test/bin/g77 -v dimstar.f
Reading specs from
/usr/test/lib/gcc-lib/m68k-next-nextstep3/egcs-2.91.02/specs
gcc version egcs-2.91.02 971206 (gcc-2.8.0)
/usr/test/lib/gcc-lib/m68k-next-nextstep3/egcs-2.91.02/f771
dimstar.f -fset-g77-defaults -quiet -dumpbase dimstar.f -version
-fversion -o /usr/tmp/cc020259.s
GNU F77 version egcs-2.91.02 971206 (gcc-2.8.0)
(m68k-next-nextstep3) compiled by GNU C version egcs-2.91.02 971206
(gcc-2.8.0).
GNU Fortran Front End version 0.5.22-19970929
dimstar.f: In subroutine `star':
dimstar.f:1:
subroutine star(aap, noot)
^
Array `aap' at (^) is too large to handle
Seems that an earlier fix of this didn't make into the main
(non-release) branch.
Cheers,
Toon.
next reply other threads:[~1997-12-10 7:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-10 7:08 Toon Moene [this message]
1997-12-10 13:36 ` fortran regression [was Re: Results for egcs-971207 on m68k-next-nextstep3] Dave Love
1997-12-10 16:43 ` Jeffrey A Law
1997-12-11 11:14 ` Dave Love
1997-12-11 16:33 ` Craig Burley
1997-12-12 10:18 ` Dave Love
1997-12-12 18:04 ` Craig Burley
[not found] ` <rzqd8j2zb5m.fsf.cygnus.egcs@djlvig.dl.ac.uk>
1997-12-12 15:46 ` Jason Merrill
1997-12-13 10:44 ` Dave Love
1997-12-15 23:18 ` g77 assumed array patch [was: fortran regression] Richard Henderson
1997-12-18 23:19 ` Jeffrey A Law
1997-12-19 12:37 ` Dave Love
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=9712101506.AA20265@moene.indiv.nluug.nl \
--to=toon@moene.indiv.nluug.nl \
--cc=egcs@cygnus.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).