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@sourceware.org Subject: [Bug libc/18527] New: getlogin_r namespace Date: Fri, 12 Jun 2015 17:25:00 -0000 [thread overview] Message-ID: <bug-18527-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18527 Bug ID: 18527 Summary: getlogin_r namespace Product: glibc Version: 2.21 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: jsm28 at gcc dot gnu.org CC: drepper.fsp at gmail dot com Target Milestone: --- Various functions in XPG4 bring in references to getlogin_r, which is not in XPG4. [initial] glob -> [libc.a(glob.o)] getlogin_r [initial] getlogin -> [libc.a(getlogin.o)] __getlogin_r_loginuid -> [libc.a(getlogin_r.o)] getlogin_r [initial] wordexp -> [libc.a(wordexp.o)] glob -> [libc.a(glob.o)] getlogin_r -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-06-12 17:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-12 17:25 jsm28 at gcc dot gnu.org [this message] 2015-06-12 20:03 ` [Bug libc/18527] " jsm28 at gcc dot gnu.org 2015-06-12 20:03 ` cvs-commit 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-18527-131@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).