From: Tom Browder <tom.browder@gmail.com>
To: GCC-help <gcc-help@gcc.gnu.org>
Subject: Re: gcc-4.5.1 failing test: FAIL: 22_locale/time_get/get_date/wchar_t/4.cc execution test
Date: Fri, 10 Sep 2010 11:33:00 -0000 [thread overview]
Message-ID: <AANLkTindqfye=paFH=Q0A91hhpHrroK+-Y1mGPffVhii@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinZdYSAcFpJ-0s8gdcke0Lb17e0_gV=fGPxUWfU@mail.gmail.com>
On Thu, Sep 9, 2010 at 20:35, Tom Browder <tom.browder@gmail.com> wrote:
> After a good build of gcc-4.5.1 I did
>
> $ make check-target-libstdc++-v3
>
> and I get only one failure:
>
> Setting LD_LIBRARY_PATH to
> :/disk3/extsrc/gcc_build/gcc:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/./libstdc++-v3/../libgomp/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/./libstdc++-v3/src/.libs::/disk3/extsrc/gcc_build/gcc:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/./libstdc++-v3/../libgomp/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/./libstdc++-v3/src/.libs:/disk3/extsrc/gcc_build/./gmp/.libs:/disk3/extsrc/gcc_build/./prev-gmp/.libs:/disk3/extsrc/gcc_build/./mpfr/.libs:/disk3/extsrc/gcc_build/./prev-mpfr/.libs:/disk3/extsrc/gcc_build/./mpc/.libs:/disk3/extsrc/gcc_build/./prev-mpc/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/libstdc++-v3/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/libmudflap/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/libssp/.libs:/disk3/extsrc/gcc_build/x86_64-unknown-linux-gnu/libgomp/.libs:/disk3/extsrc/gcc_build/./gcc:/disk3/extsrc/gcc_build/./prev-gcc
> 4.exe: /disk3/extsrc/gcc-4.5.1/libstdc++-v3/testsuite/22_locale/time_get/get_date/wchar_t/4.cc:54:
> void test01(): Assertion `errorstate == ios_base::eofbit' failed.
> FAIL: 22_locale/time_get/get_date/wchar_t/4.cc execution test
>
> I am investigating but wonder if anyone has experienced that failure
> and has a solution. I am finding several undocumented factors
> (including LD_LIBRARY_PATH and some configuration options that are not
> easily found) that have an influence on successfully testing libstdc++
> and plan to propose doc changes.
Disregard, I got this answer earlier from Paolo Carlini, a libsdtdc++ developer:
<quote>
On 08/31/2010 05:02 PM, Tom Browder wrote:
> Okay, I now have only one failure:
>
> 4.exe: /disk3/extsrc/gcc-4.5.1/libstdc++-v3/testsuite/22_locale/time_get/get_date/wchar_t/4.cc:54:
> void test01(): Assertion `errorstate == ios_base::eofbit' failed.
> FAIL: 22_locale/time_get/get_date/wchar_t/4.cc execution test
>
This is / was libstdc++/31413. Everything is fine as far as I can see.
</quote>
This is a known Debian problem.
-Tom
Thomas M. Browder, Jr.
Niceville, Florida
USA
prev parent reply other threads:[~2010-09-10 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 1:36 Tom Browder
2010-09-10 11:33 ` Tom Browder [this message]
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='AANLkTindqfye=paFH=Q0A91hhpHrroK+-Y1mGPffVhii@mail.gmail.com' \
--to=tom.browder@gmail.com \
--cc=gcc-help@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: link
Be 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).