"d3a5bf95f2013af081607abd91b5175f6eafa563" (history) in projects: freebsd

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched hist:d3a5bf95f2013af081607abd91b5175f6eafa563 (Results 1 – 2 of 2) sorted by relevance

/freebsd/share/mk/
H A D	bsd.opts.mk	diff 66957ade1e577092badf838ea04b3477ac5ffa0f Sat Mar 16 00:00:46 CET 2024 Brooks Davis <brooks@FreeBSD.org> bsd.opts.mk: drop transtion aid for NO_* options Setting NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB, NO_MAN, NO_PROFILE, and NO_WARNS was deprecated in 2014 and made an error prior to the 13.0.0 release in commit d3a5bf95f2013af081607abd91b5175f6eafa563. Likewise, NO_WERROR was made an error prior to 13.0.0 in commit 7fa2f2a62f04f095e1e27ad55aa22a8f59b1df8f. Remove this transition aid making these variables no-ops as setting them will result in an error on all supported releases. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D44345 diff d3a5bf95f2013af081607abd91b5175f6eafa563 Wed Feb 12 19:09:20 CET 2020 Brooks Davis <brooks@FreeBSD.org> Make the warning for deprecated NO_ variables an error. Support for NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB, NO_MAN, NO_PROFILE, and NO_WARNS as deprecated in 2014 with a warning added for each one found. Turn these into error in preperation for removal of compatability support before FreeBSD 13. This was previously committed in r354909 and reverted in r355011 due to unforseen impacts on ports. I've since corrected all amd64 and i386 ports reported in prior runs as well as instance of these variables I found via grep.
/freebsd/
H A D	UPDATING	diff d3a5bf95f2013af081607abd91b5175f6eafa563 Wed Feb 12 19:09:20 CET 2020 Brooks Davis <brooks@FreeBSD.org> Make the warning for deprecated NO_ variables an error. Support for NO_CTF, NO_DEBUG_FILES, NO_INSTALLLIB, NO_MAN, NO_PROFILE, and NO_WARNS as deprecated in 2014 with a warning added for each one found. Turn these into error in preperation for removal of compatability support before FreeBSD 13. This was previously committed in r354909 and reverted in r355011 due to unforseen impacts on ports. I've since corrected all amd64 and i386 ports reported in prior runs as well as instance of these variables I found via grep.