Hi Thorsten, thanks for the advice. Since 200 I never needed -Wno-error, and I think it should not be necessary, so I am going through the code and fix all the occurrences and will submit my fixes to upstream.
But for my testing of the M-A changes I'll use -Wno-error for the time being. Thanks Norbert ------------------------------------------------------------------------ PREINING, Norbert http://www.preining.info JAIST, Japan TeX Live & Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13 ------------------------------------------------------------------------ > On Sep 21, 2015, at 5:52 PM, Thorsten Glaser <t...@mirbsd.de> wrote: > > Norbert Preining dixit: > >> I am now trying to build the package - without success - debhelper9 >> or gcc5 (don't know what) changed several warnings to errors > > You *really* should use -Wno-error when compiling for Debian > (as opposed to compiling for your own testing) because that’s > a given – newer versions of the toolchain *will* introduce > more warnings you could not have anticipated at the time of > upload, and this is an easy RC bug. > > bye, > //mirabilos > -- > Yay for having to rewrite other people's Bash scripts because bash > suddenly stopped supporting the bash extensions they make use of > -- Tonnerre Lombard in #nosec
