public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "web-sources dot redhat dot com at jankratochvil dot net" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/1043] New: --enable-static-nss false linking warnings Date: Sun, 03 Jul 2005 10:03:00 -0000 [thread overview] Message-ID: <20050703100346.1043.web-sources.redhat.com@jankratochvil.net> (raw) After build --disabled-shared --enable-static-nss glibc library it reports warnings intended for glibc "--disabled-shared" (or "gcc application.c -static" at all) but no longer valid for glibc built with: --enable-static-nss warning: Using 'getpwnam' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking Patch attached. -- Summary: --enable-static-nss false linking warnings Product: glibc Version: 2.3.5 Status: NEW Severity: minor Priority: P2 Component: libc AssignedTo: gotom at debian dot or dot jp ReportedBy: web-sources dot redhat dot com at jankratochvil dot net CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i386-redhat-linux-gnu GCC host triplet: i386-redhat-linux-gnu GCC target triplet: i386-redhat-linux-gnu http://sources.redhat.com/bugzilla/show_bug.cgi?id=1043 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-07-03 10:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-03 10:03 web-sources dot redhat dot com at jankratochvil dot net [this message] 2005-07-03 10:07 ` [Bug libc/1043] " web-sources dot redhat dot com at jankratochvil dot net 2005-07-03 10:42 ` web-sources dot redhat dot com at jankratochvil dot net 2005-07-19 3:47 ` roland at 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=20050703100346.1043.web-sources.redhat.com@jankratochvil.net \ --to=sourceware-bugzilla@sources.redhat.com \ --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).