public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: zack@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/6415: powerpc-wrs-vxworks wont bootstrap
Date: Mon, 22 Apr 2002 22:36:00 -0000 [thread overview]
Message-ID: <20020423053601.27216.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/6415; it has been noted by GNATS.
From: Zack Weinberg <zack@codesourcery.com>
To: kim@mso.anu.edu.au
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/6415: powerpc-wrs-vxworks wont bootstrap
Date: Mon, 22 Apr 2002 22:29:32 -0700
> > In file included from /data/mizar/kim/powerpc-wrs-vxworks/sys-include/types/vxANSI.h:44,
> > from include/stdio.h:66,
> > from ../../gcc/gcc/tsystem.h:63,
> > from ../../gcc/gcc/libgcc2.c:37:
> > include/types/vxCpu.h:209:2: #error CPU is not defined correctly
I suppose I could describe this as a "known bug", since it bit me just
this afternoon ;-)
Anyway, not likely to be fixed in the 2.95 or 3.0 branches, and won't
be fixed in 3.1.0, but I hope to have it working in 3.1.1.
zw
next reply other threads:[~2002-04-23 5:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 22:36 Zack Weinberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-04 1:07 zack
2002-04-22 22:31 zack
2002-04-22 22:06 kim
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=20020423053601.27216.qmail@sources.redhat.com \
--to=zack@codesourcery.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=zack@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).