This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug build/17956] Glibc compilation fails on missing definitions from header file nss/nss.h
- From: "g.trentalancia at libero dot it" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 30 May 2016 13:16:09 +0000
- Subject: [Bug build/17956] Glibc compilation fails on missing definitions from header file nss/nss.h
- Auto-submitted: auto-generated
- References: <bug-17956-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17956
g.trentalancia at libero dot it changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |g.trentalancia at libero dot it
--- Comment #7 from g.trentalancia at libero dot it ---
The situation has further degenerated after the introduction of the latest
release 2.23. An additional patch is now needed to compile glibc with the
--enable-nss-crypt option.
I suppose the two header files "nss.h" from glibc (local glibc source tree) and
"nss.h" from Mozilla NSS (usually located in /usr/include/nss3) are conflicting
and the compiler not always picks the right one (it gives precedence to the one
specified in CPPFLAGS, which is not always the right choice).
The new additional patch that is now needed and that is mentioned above is
attached.
Another solution might be to avoid passing CPPFLAGS to gcc when building those
source files that need to include the local "nss.h" instead of the Mozilla NSS
one. We have the list of such files in the two attached patches...
And the reply to Comment 5, is that of course it builds normally without
--enable-nss-crypt and the modified CPPFLAGS! The problem is that nsswitch.h
includes <nss.h> which defaults to /usr/include/nss3/nss.h when the modified
CPPFLAGS are defined. That's why the patch (or an other alternative fix) is
needed: because when the local glibc "nss.h" is needed, the source file
requiring it, should include the right one by using the relative local path and
double quotes (as in #include "../../nss/nss.h" and similar).
--
You are receiving this mail because:
You are on the CC list for the bug.