From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9428 invoked by alias); 11 Oct 2002 20:20:19 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 9421 invoked from network); 11 Oct 2002 20:20:18 -0000 Received: from unknown (HELO imo-r02.mx.aol.com) (152.163.225.98) by sources.redhat.com with SMTP; 11 Oct 2002 20:20:18 -0000 Received: from Llappin4@netscape.net by imo-r02.mx.aol.com (mail_out_v34.13.) id e.1b3.260f6f3 (22681); Fri, 11 Oct 2002 16:20:01 -0400 (EDT) Received: from netscape.net (pcp02452736pcs.verona01.nj.comcast.net [68.36.152.188]) by air-in04.mx.aol.com (v89.10) with ESMTP id MAILININ42-1011162001; Fri, 11 Oct 2002 16:20:01 -0400 Message-ID: <3DA76033.9020606@netscape.net> Date: Fri, 11 Oct 2002 15:08:00 -0000 From: damovand User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: echristo@redhat.com CC: gcc@gcc.gnu.org Subject: Re: What to do about already reported bugs References: <3DA753B2.504@netscape.net> <1034364775.3538.100.camel@ghostwheel> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-10/txt/msg00628.txt.bz2 Hi, First I want to thank the contributors to gcc library. As an application developer I was never aware of the complexities of issues at the compiler level. Now I'm finding out ... Currently I'm running through the post install tests using 'make test' or in my case mkcheck. I found undefined reference in the following (std::codecvt, std::char_traits, std::ctype, std::moneypunct, std::numpunct, pthread_join) I'm not worried about the bugs as long as I can develop my application. Thanks. echristo@redhat.com wrote: > On Fri, 2002-10-11 at 15:41, damovand wrote: > >>Hi everyone, >> >>First thanks to those of you who responded to my first question, I found >>the documentation link. >> >>I tested my build by using 'mkcheck 0' command and found a list of >>failures as reported on http://gcc.gnu.org/testresults/cs132.html (for >>i686-pc-linux-gnu). Since these bugs still can I still use the >>compiler? I found a number of posts regarding one of the bugs, >>char_traits, but my searches haven't turned up anything regarding what >>to do about it. >> >> > > Yes, all known compilers have bugs - ours just lets you find out the > ones we already know about via a testsuite ;) > > re: char_traits - could you post a testcase of what you are trying to > do? > > -eric > > >