This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcc/77470] libssp may have bad includes
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 05 Sep 2016 11:03:14 +0000
- Subject: [Bug libgcc/77470] libssp may have bad includes
- Auto-submitted: auto-generated
- References: <bug-77470-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77470
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The ssp headers are meant to be used together with -D_FORTIFY_SOURCE{,=2}
-isystem .../include/ssp/
They are meant to override the system stdio.h, string.h and/or unistd.h
headers, which they include as #include_next.
So this looks like a user error, or maybe NetBSD header bug.
Of course, if _FORTIFY_SOURCE support is in your C library, you don't need any
of the libssp headers.