List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
El lun, 14-05-2012 a las 20:24 +0200, Jeroen Roovers escribió:
> On Mon, 14 May 2012 18:01:22 +0200
> Chí-Thanh Christopher Nguyễn <email@example.com> wrote:
> > -Werror is basically saying that it is not safe to ship code which
> > produces warnings.
> An upstream demanding -Werror should work means upstream would need to
> test rather a lot more than their own favourite
> distro/architecture/library versions/kernel/userland, which isn't
> going to happen.
> > I personally think that if an upstream says that no warnings must be
> > produced by the code, and a developer should look at them before
> > declaring any warnings safe, then that is best followed.
> Upstream does not need to take into account warnings produced by
> compilers for lesser known architectures, as explained above.
> As an upstream development aid to check code that has just been added
> or changed, -Werror is fine, but not in the wild jungle that is Gentoo.
> You might as well just look at the warnings themselves instead of
> breaking the build system by making them fatal. In other words, for
> upstream development it's convenient, but never for our users out there.
> Also, bug reports based on *FLAGS=-Werror will be closed as INVALID.
> (Perhaps we should document that too.)
I fully agree with Jeroen on this, -Werror problems should be reported
directly to upstream if people want to help them on fixing warnings.
signature.asc (This is a digitally signed message part)