public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Janis Johnson <janis187@us.ibm.com>
Cc: gcc@gcc.gnu.org, mark@codesourcery.com
Subject: Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?
Date: Fri, 04 Oct 2002 09:56:00 -0000	[thread overview]
Message-ID: <20021004094724.A20284@lucon.org> (raw)
In-Reply-To: <20021004094556.A1711@us.ibm.com>; from janis187@us.ibm.com on Fri, Oct 04, 2002 at 09:45:56AM -0700

On Fri, Oct 04, 2002 at 09:45:56AM -0700, Janis Johnson wrote:
> On Thu, Oct 03, 2002 at 11:59:22PM -0700, H. J. Lu wrote:
> > With Thu Oct  3 23:25:02 PDT 2002's 3.2 branch, I got
> > 
> > /export/build/gnu/gcc-3.2/build-i686-linux/i686-pc-linux-gnu/libstdc++-v3/include/ext/stl_rope.h:609: no
> >    type named `allocator_type' in `struct __gnu_cxx::_Rope_rep_base<char, 
> >    std::allocator<char> >'
> 
> I got the same failure last night on ia64-unknown-linux-gnu with the
> 3.2 branch.
> 

Mark, Andreas has identified your patch breaks both mainline and 3.2:

http://gcc.gnu.org/ml/gcc/2002-10/msg00231.html

Shouldn't we revert it at least on the 3.2 branch?


H.J.

  reply	other threads:[~2002-10-04 16:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-04  1:59 H. J. Lu
2002-10-04  6:03 ` kwall
2002-10-04  9:51 ` Janis Johnson
2002-10-04  9:56   ` H. J. Lu [this message]
2002-10-04 10:05     ` H. J. Lu
2002-10-04 11:43       ` PATCH: Revert part of c++ change (Re: Does gcc 3.2 branch bootstrap on RedHat 7.3?) H. J. Lu
2002-10-05  3:33     ` Does gcc 3.2 branch bootstrap on RedHat 7.3? Andreas Tobler
2002-10-05  4:00       ` Andreas Jaeger
2002-10-05 11:21         ` Fergus Henderson
2002-10-05 13:56           ` Andreas Jaeger
2002-10-06  0:12             ` Fergus Henderson
2002-10-08  3:02           ` Mark Mitchell

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=20021004094724.A20284@lucon.org \
    --to=hjl@lucon.org \
    --cc=gcc@gcc.gnu.org \
    --cc=janis187@us.ibm.com \
    --cc=mark@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).