public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/6528] New: Fixes for --enable-static-nss Date: Fri, 16 May 2008 17:44:00 -0000 [thread overview] Message-ID: <20080516174338.6528.drow@sources.redhat.com> (raw) I'll attach a patch that fixes glibc build with --enable-static-nss and makes it usable by automatically including the necessary libraries in libc.a. Otherwise compile flags for every application have to be changed to include -lnss_files -lnss_dns -lresolv or else there are link errors from any NSS use. I realize the option is not supported. Since the fix mostly deletes code I figured I'd submit it anyway. I used bugzilla despite the comment in bug 631, since the policy seems to have changed since 2005; the glibc maintainers tell people to put patches in Bugzilla now. If you'd prefer this on libc-alpha just close it and I'll post there. -- Summary: Fixes for --enable-static-nss Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: roland at gnu dot org ReportedBy: drow at sources dot redhat dot com CC: glibc-bugs at sources dot redhat dot com,jan dot kratochvil at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=6528 ------- 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:[~2008-05-16 17:44 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-05-16 17:44 drow at sources dot redhat dot com [this message] 2008-05-16 17:44 ` [Bug libc/6528] " drow at sources dot 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=20080516174338.6528.drow@sources.redhat.com \ --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).