src/lib/libc/secure, branch release/11.1.0 FreeBSD source tree libc: do not include <sys/types.h> where <sys/param.h> was already included 2016-04-18T21:05:15+00:00 Andriy Voskoboinyk avos@FreeBSD.org 2016-04-18T21:05:15+00:00 2cf5e9365d299ad70ec7fe8a7e7202fbb925e70c According to style(9): > normally, include <sys/types.h> OR <sys/param.h>, but not both. (<sys/param.h> already includes <sys/types.h> when LOCORE is not defined). 
According to style(9):
> normally, include <sys/types.h> OR <sys/param.h>, but not both.
(<sys/param.h> already includes <sys/types.h> when LOCORE is not defined).
libc: don't build compat functions if building WITHOUT_SYMVER 2016-03-15T19:26:32+00:00 Ed Maste emaste@FreeBSD.org 2016-03-15T19:26:32+00:00 c38dac681dc4870327a8b734c94a436968e2bd9d WITHOUT_SYMVER necessarily implies building a system without symver backwards compatability. Sponsored by: The FreeBSD Foundation 
WITHOUT_SYMVER necessarily implies building a system without symver
backwards compatability.

Sponsored by:	The FreeBSD Foundation
Remove a stale comment and clarify the original where it was taken from 2015-08-14T14:58:04+00:00 Pedro F. Giffuni pfg@FreeBSD.org 2015-08-14T14:58:04+00:00 842898ceec3de25a38d2e2397ca19f5357cb070c The comment in the libc/sys symbol map referenced the generated symbols for the syscall trampolines. Such comment was out of place in the secure symbol map so remove the stale comment and attempt to clarify the old one to avoid risks of confusion. Pointed out by: kib 
The comment in the libc/sys symbol map referenced the generated symbols
for the syscall trampolines. Such comment was out of place in the secure
symbol map so remove the stale comment and attempt to clarify the old one
to avoid risks of confusion.

Pointed out by:	kib
Move the stack protector to a new "secure" directory 2015-08-14T03:03:13+00:00 Pedro F. Giffuni pfg@FreeBSD.org 2015-08-14T03:03:13+00:00 fe0d386cf33928c3b3839bc428f304d38e979803 As part of the code refactoring to support FORTIFY_SOURCE we want a new subdirectory "secure" to keep the files related to security. Move the stack protector functions to this new directory. No functional change. Differential Review: https://reviews.freebsd.org/D3333 
As part of the code refactoring to support FORTIFY_SOURCE we want
a new subdirectory "secure" to keep the files related to security.
Move the stack protector functions to this new directory.

No functional change.

Differential Review:	https://reviews.freebsd.org/D3333