GNU-compatible, BSD-licensed bc

[Devin Teske]

> On Jan 9, 2019, at 3:04 PM, Rebecca Cran <rebecca at bluestop.org> wrote:
> 
> On January 9, 2019 at 4:02:57 PM, Devin Teske (dteske at freebsd.org <mailto:dteske at freebsd.org>) wrote:
> 
>> 
>> Yes. -Weverything is the strictest I have ever seen. 
>> 
>> Often times I find that software cannot be compiled with -Weverything despite 
>> passing -Wall -Wextra because some of the system/library headers fail checks. 
>> 
>> I've often considered a great accomplishment when I can pass -Weverything.
> From https://embeddedartistry.com/blog/2017/3/7/clang-weverything <https://embeddedartistry.com/blog/2017/3/7/clang-weverything> :
> 
> “Clang helpfully provides a flag called -Weverything. Unlike -Wall, the -Weverything flag really will enable all warnings. This flag is especially useful if you are a warning lover - new warnings will automatically be enabled when you upgrade clang/Xcode. 
> 
> Turning -Weverything can be an eye-opening experience, even for those who religiously squash warnings. I often turn on -Weverything temporarily to review any of the less-common warnings and see what's worth fixing in my code base.”
> 
> 
> 
With few exceptions, I've made it the default for one of my latest projects:

https://github.com/FrauBSD/pkgcenter/blob/master/depend/libcmb/configure.in <https://github.com/FrauBSD/pkgcenter/blob/master/depend/libcmb/configure.in>

AS_IF(test "$CC" = clang, [
	CFLAGS="${CFLAGS:+$CFLAGS }$( echo \
		-Weverything \
		-Wno-extra-semi \
		-Wno-padded \
		-Wno-reserved-id-macro \
		-Wno-unused-macros \
	)"
])

-- 
Devin