Re: libstdc++/10217: problem in building libstdc++-v3

["Marwijn Hessel" <mwhessel at xs4all dot nl>]

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

From: "Marwijn Hessel" <mwhessel at xs4all dot nl>
To: <ehrhardt at mathematik dot uni-ulm dot de>, <gcc-bugs at gcc dot gnu dot org>,
   <gcc-prs at gcc dot gnu dot org>, <marwijn dot hessel at ict dot nl>, <nobody at gcc dot gnu dot org>,
   <gcc-gnats at gcc dot gnu dot 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 at mathematik dot uni-ulm dot de>
 To: <gcc-bugs at gcc dot gnu dot org>; <gcc-prs at gcc dot gnu dot org>; <marwijn dot hessel at ict dot nl>;
 <nobody at gcc dot gnu dot 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 at ICT dot 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.
 >
 >
 >
 >
 >