public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matt_Conway@i2.com
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2700
Date: Fri, 18 May 2001 08:26:00 -0000 [thread overview]
Message-ID: <20010518152601.10785.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/2700; it has been noted by GNATS.
From: Matt_Conway@i2.com
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2700
Date: Fri, 18 May 2001 14:11:05 -0400
No - I sent you this mail because I was NOT having any luck =)
Since I assumed the problem was something with libstdc++ and not the
compiler (or the combinaton), I had tried the libstdc++ from the main
branch with the compiler from the 3.0 branch and it still failed.
I can go grab the main branch again now, and try it if you think its a
problem thats related to the compiler as well as libstdc++.
You'll have to patient though, it takes me a good 12-24 hours to bootstrap
- configure of libstdc++ being the main culprit - is there anyway to not
have to reconfigure everytime I update from cvs?
Matt
Benjamin Kosnik <bkoz@redhat.com>
05/18/01 02:36 AM
To: Matt_Conway@i2.com
cc: gcc-gnats@gcc.gnu.org
Subject: Re: libstdc++/2700
Any luck? It seems like the branch is updated and working now.
next reply other threads:[~2001-05-18 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-18 8:26 Matt_Conway [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 23:46 libstdc++/2700 Benjamin Kosnik
2001-05-08 23:46 libstdc++/2700 bkoz
2001-05-04 12:46 libstdc++/2700 Benjamin Kosnik
2001-05-04 12:26 libstdc++/2700 Benjamin Kosnik
2001-05-02 12:06 libstdc++/2700 bkoz
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=20010518152601.10785.qmail@sourceware.cygnus.com \
--to=matt_conway@i2.com \
--cc=bkoz@gcc.gnu.org \
--cc=gcc-prs@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).