Hi!
So in principle, the default compiler in Debian is gcc, and the
default flags up to now have been targeting that, plus the specific
gcc version that is the current default. So packages using clang have
had to amend those flags by themselves.
Hmm that's unfortunate.
Is that being used or packaged in Debian? (Just curious.)
Unfortunately I don't think there's a machine readable way to discern
between them, that might not involve either parsing stuff like
--version/--help or pre-processing or compiling a program, which
seem rather undesirable. This would probably need to be specified by
the caller somehow.
I've got some pending discussion in the works for a revamp of the
build flags handling, which includes also trying to cover multiple
toolchains, which would hopefully cover this case. But as it is, I'd
say as of now, packages that use something that is not the default
compiler at the expected version, are on their own.
I tried to look for that in Debian and could not find it, do you have
a pointer? But in any case, while I think supporting other toolchains
would be ideal and worthwhile, building packages with blanket -Werror
has always seemed like a bad idea because it then can cause this sort
of thing (or other unexpected errors due to newly introduced warnings).
Thanks,
Guillem