This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Unresolved Check Error
- From: Phil Edwards <phil at jaj dot com>
- To: Mike Cleary <mcleary at iol dot unh dot edu>
- Cc: libstdc++ at gcc dot gnu dot org, clp <clp at iol dot unh dot edu>
- Date: Mon, 26 Aug 2002 14:44:54 -0400
- Subject: Re: Unresolved Check Error
- References: <3D6A7548.4000008@iol.unh.edu>
On Mon, Aug 26, 2002 at 02:36:56PM -0400, Mike Cleary wrote:
> but I wasn't even responded to when I asked for help.
Sorry, we've been a bit busy lately.
> How do I test the individual macros?
I'm assuming you're talking about
> >>FAIL: 26_numerics/c99_classification_macros_c.cc (test for excess errors)
> >
> >C library issue. Interfacing with arbitrary C libraries is difficult.
as opposed to some other kind of macro. Probably the easiest low-tech
solution is to edit
(srcdir)/libstdc++-v3/testsuite/26_numerics/c99_classification_macros_c.cc
and comment out all calls but one. Viewing the
(builddir)/alphawhatever/libstdc++-v3/testsuite/libstdc++-v3.log file
to check the exact error messages also usually helps. (The testsuite
harness sinks compiler output into that file, and only displays the "test
for excess errors".)
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002