public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <pedwards@disaster.jaj.com>
To: pme@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2071
Date: Tue, 12 Jun 2001 16:36:00 -0000	[thread overview]
Message-ID: <20010612233600.20339.qmail@sourceware.cygnus.com> (raw)

The following reply was made to PR libstdc++/2071; it has been noted by GNATS.

From: Phil Edwards <pedwards@disaster.jaj.com>
To: rittle@labs.mot.com
Cc: bkoz@redhat.com, mark@codesourcery.com, gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2071
Date: Tue, 12 Jun 2001 18:15:39 -0400

 In two different messages, Loren James Rittle wrote:
 > Phil reported ( http://gcc.gnu.org/ml/libstdc++/2001-06/msg00071.html )
 > that it didn't work for him on Solaris 2.8, but I am not convinced yet
 > that it wasn't something minor (and/or the insidious Makefile problem
 > - I don't know Phil's habits when it comes to applying a patch and
 > attempting a rebuild in an already bootstrapped tree
 
 My habits usually involve 'rm -rf' at a couple of points, since we aren't
 explicitly tracking dependencies yet.  Automake helps, but you never know.
 
 
 > Patch applied to mainline and 3.0 branch.  I will close it in GNATS on
 > Wednesday assuming no issues surface.
 
 Cool.  I'm just now getting to a computer and reading all my mail, including
 this GNATS thread.  I'll test the patch on my sol8 box just for kicks this
 evening, and will report, but don't hold things up on my account.
 
 
 Phil
 
 -- 
 pedwards at disaster dot jaj dot com  |  pme at sources dot redhat dot com
 devphil at several other less interesting addresses in various dot domains
 The gods do not protect fools.  Fools are protected by more capable fools.


             reply	other threads:[~2001-06-12 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-12 16:36 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-12 16:26 libstdc++/2071 Loren James Rittle
2001-06-12 13:26 libstdc++/2071 Benjamin Kosnik
2001-06-12  2:06 libstdc++/2071 Mark Mitchell
2001-06-12  1:56 libstdc++/2071 Loren James Rittle
2001-06-11 19:06 libstdc++/2071 Benjamin Kosnik
2001-06-05 13:16 libstdc++/2071 pme

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=20010612233600.20339.qmail@sourceware.cygnus.com \
    --to=pedwards@disaster.jaj.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=pme@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).