public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/14767] New: Dead tests of have-initfini-array in elf/Makefile Date: Thu, 25 Oct 2012 19:41:00 -0000 [thread overview] Message-ID: <bug-14767-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14767 Bug #: 14767 Summary: Dead tests of have-initfini-array in elf/Makefile Product: glibc Version: 2.16 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: unassigned@sourceware.org ReportedBy: jsm28@gcc.gnu.org CC: drepper.fsp@gmail.com Classification: Unclassified elf/Makefile contains code that enables some testcases if $(have-initfini-array) is "yes". Nothing sets such a variable. I'd guess from the name that these should nowadays be enabled unconditionally, but haven't tested this. Note that the tests aren't cross-testing ready (they have ad hoc testing rules that need $(test-wrapper) added) - that's how I spotted this issue (noticing the test rules that hadn't been included in the cross-testing changes, but hadn't resulted in any test failures for cross-testing either). It's quite possible, if these tests haven't been run for a long time, that they are bitrotten in other ways as well. -- 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 reply other threads:[~2012-10-25 19:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-25 19:41 jsm28 at gcc dot gnu.org [this message] 2012-10-25 22:52 ` [Bug libc/14767] " schwab@linux-m68k.org 2012-10-30 8:12 ` aj at suse dot de 2012-11-04 0:15 ` hjl.tools at gmail dot com 2014-06-14 11:18 ` 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-14767-131@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: linkBe 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).