Richard PALO <richard%netbsd.org@localhost> writes:
> Again, I'd like to update clang.mk making c99, c11 and c++11 use the
> same -std=gnu* as gcc.mk. I wonder if perhaps adding -Wpedantic is
> worthwhile.
I don't see why this is reasonable. Programs should be written to
standards, not gcc extensions. It may be that we should have a
package-settable variable to note that the package is in gnu c dialect
instead of a standard one. Or that may be tilting at windmills.
The other quesion is what packages are failing to build under clang due
to not having this, but do with it, and how many of them are there?
> It would be trivial to add, if deemed usefule, a package settable
> variable such as GCC_STRICT_ANSI to force -std={c99,c11,c++11} instead
> of the gnu extension variant.
At first glance, I think that's backwards.
But we need to understand which packages have issues, what kind, and how
many.
Attachment:
signature.asc
Description: PGP signature