From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2191 invoked by alias); 3 Apr 2003 15:56:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 2177 invoked by uid 71); 3 Apr 2003 15:56:00 -0000 Date: Thu, 03 Apr 2003 15:56:00 -0000 Message-ID: <20030403155600.2176.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Marwijn Hessel" Subject: Re: libstdc++/10217: problem in building libstdc++-v3 Reply-To: "Marwijn Hessel" X-SW-Source: 2003-04/txt/msg00094.txt.bz2 List-Id: The following reply was made to PR libstdc++/10217; it has been noted by GNATS. From: "Marwijn Hessel" To: , , , , , 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: To: ; ; ; 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. > > > > >