Re: How to pass CFLAGS to upstream's Makefile with debhlepler ?
* Nicolas Bourdaud <nicolas.bourdaud@gmail.com> [111114 15:25]:
> On 14/11/2011 14:32, Bernhard R. Link wrote:
> > Without -Wall you won't get some of the most "critical" warnings.
> > A package should really not be built without at least -Wall.
>
> I understand, and I think it is a pity that some software produce way
> too many warnings when compiled with -Wall and -Wextra.
>
> However is it not already too late to catch those warnings when the
> package is being built? IMO, they should have been taken care in
> upstream.
While it might be to late for this package, it is not yet too late for
the next version of a package. Or to use the informationen when looking
for the cause of bugs.
Especially when looking for bugs only showing up on some architectures
(like working on 32 bit but failing on 64 bit) and the like.
> Or do you consider to *massively* patch the source to fix the warnings?
Depends on the type of warnings. But there are definitely cases where
that is called for. (And hopefully those warnings accepted upstream if
there still is a upstream).
Bernhard R. Link
Reply to: