public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Marwijn Hessel" <mwhessel@xs4all.nl> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/10217: problem in building libstdc++-v3 Date: Thu, 03 Apr 2003 15:56:00 -0000 [thread overview] Message-ID: <20030403155600.2176.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/10217; it has been noted by GNATS. From: "Marwijn Hessel" <mwhessel@xs4all.nl> To: <ehrhardt@mathematik.uni-ulm.de>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <marwijn.hessel@ict.nl>, <nobody@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: libstdc++/10217: problem in building libstdc++-v3 Date: Thu, 3 Apr 2003 17:47:11 +0200 Hi, Nice that is not a wanted bug ... But what is the solution ???? Regards, Marwijn ----- Original Message ----- From: <ehrhardt@mathematik.uni-ulm.de> To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <marwijn.hessel@ict.nl>; <nobody@gcc.gnu.org> Sent: Thursday, April 03, 2003 5:37 PM Subject: Re: libstdc++/10217: problem in building libstdc++-v3 > > Synopsis: problem in building libstdc++-v3 > > State-Changed-From-To: open->closed > State-Changed-By: cae > State-Changed-When: Thu Apr 3 15:37:15 2003 > State-Changed-Why: > Indeed. This is even covered by the "Bugs we don't want" section > at http://gcc.gnu.org/bugs.html#dontwant hence I'm closing this. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217 > > ---------------- > This E-mail message, including any attached documentation, is > confidential. Should you have received this message wrongly, you are > urged to inform the sender at "disclaimer@ICT.nl" and remove the message > from your system. Any unauthorised dissemination of the information, in > whole or in part, is prohibited. E-mail messages can be subject to > change. ICT Automatisering NV and its subsidiaries cannot be held > responsible for incorrect, incomplete and/or delayed transfer of > messages and possible damage caused by this. Although ICT Automatisering > NV (including its subsidiaries) makes every effort to send messages free > of viruses by using a viruschecker, ICT Automatisering NV (or its > subsidiaries) cannot guarantee that the message and any attachments are > actually completely virus free. > > > > >
next reply other threads:[~2003-04-03 15:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-03 15:56 Marwijn Hessel [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-10 9:37 rearnsha 2003-04-04 8:36 Christian Ehrhardt 2003-04-04 2:35 ljrittle 2003-04-03 16:46 Marwijn Hessel 2003-04-03 16:16 Christian Ehrhardt 2003-04-03 15:37 ehrhardt
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=20030403155600.2176.qmail@sources.redhat.com \ --to=mwhessel@xs4all.nl \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).