Re: build warnings treated as failures
Taking this topic forward, I also reached out to upstream folks, asking
them to fix these build errors on various architectures.
I already did an upload of -3 and -4 to experimental. And I still see
newer build failures popping up.
My question to rest of the folks: How do you guys cope up with foreign
architectures, for which you do not have direct access to the box?
On Wednesday 17 July 2013 11:03 PM, Guillem Jover wrote:
> On Wed, 2013-07-17 at 19:15:42 +0200, Samuel Thibault wrote:
>> Ritesh Raj Sarraf, le Wed 17 Jul 2013 22:38:51 +0530, a écrit :
>>> I see a sudden surge of build failures against my latest upload of
>>> packages. From the build logs, it looks like all warnings are treated
>>> as errors now.
>>> If that is the case, I would like to know how others are dealing with
>>> it? Fixing every build warning????
>> See configure.ac in your package:
>> AM_INIT_AUTOMAKE([-Wall -Werror foreign])
> Actually, those are automake options dealing with automake warnings.
> The culprit here is in Makefile.am (AM_CFLAGS).
>> You probably want to remove -Werror and tell upstream that it's not so
>> good an idea.
> True (for both automake and compiler warnings), at least for release
> builds, as new warnings might suddenly appear with new toolchains.
Given the large number of mailing lists I follow, I request you to CC me
in replies for quicker response