From: Carlo Wood <carlo@alinoe.com>
To: gcc@gcc.gnu.org
Cc: roger@eyesopen.com, zack@codesourcery.com
Subject: Someone broke bootstrap
Date: Wed, 08 Oct 2003 02:11:00 -0000 [thread overview]
Message-ID: <20031008021154.GA28950@alinoe.com> (raw)
gcc -c -g -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -fno-common -DHAVE_CONFIG_H -I. -I. -I../../../gcc/gcc-mainline/gcc -I../../../gcc/gcc-mainline/gcc/. -I../../../gcc/gcc-mainline/gcc/../include ../../../gcc/gcc-mainline/gcc/optabs.c -o optabs.o
../../../gcc/gcc-mainline/gcc/optabs.c: In function `prepare_float_lib_cmp':
../../../gcc/gcc-mainline/gcc/optabs.c:3886: `eqhf2_libfunc' undeclared (first use in this function)
../../../gcc/gcc-mainline/gcc/optabs.c:3886: (Each undeclared identifier is reported only once
../../../gcc/gcc-mainline/gcc/optabs.c:3886: for each function it appears in.)
../../../gcc/gcc-mainline/gcc/optabs.c:3890: `nehf2_libfunc' undeclared (first use in this function)
../../../gcc/gcc-mainline/gcc/optabs.c:3894: `gthf2_libfunc' undeclared (first use in this function)
../../../gcc/gcc-mainline/gcc/optabs.c:3899: `lthf2_libfunc' undeclared (first use in this function)
../../../gcc/gcc-mainline/gcc/optabs.c:3904: `gehf2_libfunc' undeclared (first use in this function)
../../../gcc/gcc-mainline/gcc/optabs.c:3909: `lehf2_libfunc' undeclared (first use in this function)
etc etc.
Guys, aren't we doing bootstraps anymore before a commit?
--
Carlo Wood <carlo@alinoe.com>
next reply other threads:[~2003-10-08 2:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-08 2:11 Carlo Wood [this message]
2003-10-08 13:02 ` Solved! (was: Re: Someone broke bootstrap) Carlo Wood
2003-10-08 2:47 Someone broke bootstrap John David Anglin
2003-10-08 10:15 ` David Ayers
2003-10-08 11:57 ` Carlo Wood
[not found] <no.id>
2003-10-08 3:11 ` John David Anglin
2003-10-08 7:25 ` Eric Christopher
2003-10-08 17:26 ` John David Anglin
2003-10-08 14:03 Kelley Cook
2003-10-09 3:02 Roger Sayle
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=20031008021154.GA28950@alinoe.com \
--to=carlo@alinoe.com \
--cc=gcc@gcc.gnu.org \
--cc=roger@eyesopen.com \
--cc=zack@codesourcery.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).