public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/18532] gethostbyaddr in6addr_any, in6addr_loopback namespace Date: Sun, 14 Jun 2015 14:33:00 -0000 [thread overview] Message-ID: <bug-18532-131-ZvAZUpAkg6@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-18532-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=18532 --- Comment #1 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU C Library master sources". The branch, master has been updated via bf1435783d5031e54f2f74ba3028db3c225a9da8 (commit) from 3164bf09f529754216eebfa66a5c32ce84eaec25 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=bf1435783d5031e54f2f74ba3028db3c225a9da8 commit bf1435783d5031e54f2f74ba3028db3c225a9da8 Author: Joseph Myers <joseph@codesourcery.com> Date: Sun Jun 14 14:32:07 2015 +0000 Fix linknamespace expectations for in6addr_any, in6addr_loopback. Some linknamespace test failures turned out to be because the variables in6addr_any and in6addr_loopback weren't listed in the lists of extra reserved symbols for the relevant standards (only functions are handled automatically through -aux-info, data symbols need listing manually in list-header-symbols.pl). This patch duly adds those symbols to those lists (there are still failures for older standards because of references to those symbols being brought in for standards that didn't reserve them: bug 18532, to be fixed separately). Tested for x86_64. * conform/list-header-symbols.pl (%extra_syms): Add in6addr_any and in6addr_loopback for XOPEN2K, XOPEN2K8 and POSIX2008. * conform/Makefile (test-xfail-XOPEN2K/netdb.h/linknamespace): Remove variable. (test-xfail-POSIX2008/netdb.h/linknamespace): Likewise. (test-xfail-XOPEN2K8/netdb.h/linknamespace): Likewise. ----------------------------------------------------------------------- Summary of changes: ChangeLog | 9 +++++++++ conform/Makefile | 3 --- conform/list-header-symbols.pl | 7 ++++--- 3 files changed, 13 insertions(+), 6 deletions(-) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2015-06-14 14:33 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-14 14:19 [Bug network/18532] New: " jsm28 at gcc dot gnu.org 2015-06-14 14:33 ` cvs-commit at gcc dot gnu.org [this message] 2015-06-17 20:09 ` [Bug network/18532] " cvs-commit at gcc dot gnu.org 2015-06-17 20:23 ` jsm28 at gcc dot gnu.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=bug-18532-131-ZvAZUpAkg6@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: 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).