From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Thomas Monjalon
<thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH v2] mk: Only default to -Werror when building from git checkout
Date: Fri, 20 Feb 2015 18:15:40 -0800 [thread overview]
Message-ID: <20150220181540.3b97dc86@urahara> (raw)
In-Reply-To: <9190554.3JBlDK3N1R@xps13>
On Fri, 20 Feb 2015 13:15:38 +0100
Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org> wrote:
> 2015-02-12 17:18, Panu Matilainen:
> > Add RTE_DEVEL_BUILD make-variable which can be used to do things
> > differently when doing development vs building a release,
> > autodetected from source root .git presence and overridable via
> > commandline. Use it to only enable -Werror compiler flag when
> > building a git checkout:
> >
> > Failing build on warnings is a useful developer tool but its bad
> > for release tarballs which can and do get built with newer
> > compilers than what was used/available during development. Compilers
> > routinely add new warnings so code which built silently with cc X
> > might no longer do so with X+1. This doesn't make the existing code
> > any more buggier and failing the build in this case does not help
> > not help improve code quality of an already released version either.
>
> Please, could you update documentation to explain RTE_DEVEL_BUILD option?
> Some users could try to build from git, so we should advise to disable RTE_DEVEL_BUILD.
> These files might be updated:
> http://dpdk.org/browse/dpdk/tree/doc/build-sdk-quick.txt
> http://dpdk.org/browse/dpdk/tree/doc/guides/linux_gsg/build_dpdk.rst
> http://dpdk.org/browse/dpdk/tree/doc/guides/freebsd_gsg/build_dpdk.rst
> http://dpdk.org/browse/dpdk/tree/doc/guides/prog_guide/dev_kit_build_system.rst
>
> Thanks
Also do not allow any patches to into upstream that cause
new warnings with latest stable version of Gcc or Clang?
I don't want a clean project to get littered with warning graffiti.
Maybe a build bot?
next prev parent reply other threads:[~2015-02-21 2:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 11:13 [PATCH] Make -Werror optional Panu Matilainen
[not found] ` <09445d1715453b2eff4399da998717b967b829b3.1423739602.git.pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-12 11:25 ` Bruce Richardson
2015-02-12 12:02 ` Panu Matilainen
[not found] ` <54DC964B.3050709-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-12 12:08 ` Bruce Richardson
2015-02-12 13:58 ` Panu Matilainen
[not found] ` <54DCB16F.7080104-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-12 14:02 ` Bruce Richardson
2015-02-12 14:05 ` Thomas Monjalon
2015-02-12 15:18 ` [PATCH v2] mk: Only default to -Werror when building from git checkout Panu Matilainen
[not found] ` <65cbd71d3b5b45f469a2fe67fe8b0def4bddebbd.1423754231.git.pmatilai-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-20 12:15 ` Thomas Monjalon
2015-02-21 2:15 ` Stephen Hemminger [this message]
2015-02-21 10:48 ` Thomas Monjalon
2016-03-02 14:22 ` [PATCH v3] mk: stop on warning only in developer build Thomas Monjalon
2016-03-02 22:04 ` Bruce Richardson
2016-03-03 10:36 ` Thomas Monjalon
2016-03-03 10:53 ` Panu Matilainen
2015-02-12 14:38 ` [PATCH] Make -Werror optional Stephen Hemminger
[not found] ` <20150212063820.436b2221-CA4OZQ/Yy2Lykuyl+CZolw@public.gmane.org>
2015-02-12 14:54 ` Panu Matilainen
[not found] ` <54DCBEB4.30005-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-21 1:55 ` Stephen Hemminger
2015-02-21 19:33 ` Neil Horman
[not found] ` <20150221193339.GA17802-0o1r3XBGOEbbgkc5XkKeNuvMHUBZFtU3YPYVAmT7z5s@public.gmane.org>
2015-02-23 8:19 ` Panu Matilainen
[not found] ` <54EAE28B.3070807-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-02-23 13:55 ` Neil Horman
[not found] ` <20150223135508.GB19230-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-02-23 14:20 ` Panu Matilainen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150220181540.3b97dc86@urahara \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.