public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aj at suse dot de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14358] 2.14.1: many tests failed
Date: Thu, 12 Jul 2012 12:56:00 -0000 [thread overview]
Message-ID: <bug-14358-131-0cplsYlNxj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14358-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14358
Andreas Jaeger <aj at suse dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |aj at suse dot de
Resolution| |WONTFIX
--- Comment #2 from Andreas Jaeger <aj at suse dot de> 2012-07-12 12:55:57 UTC ---
Sorry, that's not enough details. Just one comment: Don't use -Wl,--as-needed
for the testsuite.
Version 2.14.1 is old, we're not going to investigate test suite failures from
that version, please check the current 2.16 version.
For glibc 2.16, we have documented known test failures at:
http://sourceware.org/glibc/wiki/Release/2.16
If you have additional failures with glibc 2.16, please file a single report
for each failure after investigating a bit more what fails.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2012-07-12 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 12:44 [Bug libc/14358] New: " wbrana at gmail dot com
2012-07-12 12:51 ` [Bug libc/14358] " joseph at codesourcery dot com
2012-07-12 12:56 ` joseph at codesourcery dot com
2012-07-12 12:56 ` aj at suse dot de [this message]
2014-06-17 19:01 ` fweimer at redhat dot com
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=bug-14358-131-0cplsYlNxj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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).