public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bkoz at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/39382] FAIL: abi_check on trunk revision 144629
Date: Thu, 16 Apr 2009 22:11:00 -0000	[thread overview]
Message-ID: <20090416221139.5912.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39382-13830@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from bkoz at gcc dot gnu dot org  2009-04-16 22:11 -------

I suspect this is a mis-configuration of your tester. From the most current
test results:
http://gcc.gnu.org/ml/gcc-testresults/2009-04/msg00745.html

This differs in the abi_check fail from other i686 testers, which are fine.

To know the details of why abi_check fails, you'd need to examine the generated
libstdc++.log file, and look for abi_check. There will be a bunch of symbols
either added, missing, etc.

My off-hand guess is that you are missing the gnu locale stuff. To fix,
configure with

--enable-clocale=gnu

from:
http://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html

You might want to start with configuring with known good options and trying to
replicate passing results. See these baselines:

http://gcc.gnu.org/ml/gcc-testresults/2009-04/msg01677.html
http://gcc.gnu.org/ml/gcc-testresults/2009-04/msg01678.html


best,
benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39382


  reply	other threads:[~2009-04-16 22:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 12:20 [Bug libstdc++/39382] New: " rob1weld at aol dot com
2009-04-16 22:11 ` bkoz at gcc dot gnu dot org [this message]
2009-04-27 23:07 ` [Bug libstdc++/39382] " bkoz at gcc dot gnu dot org
2009-05-04 22:33 ` bkoz at gcc dot gnu dot org

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=20090416221139.5912.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).