On 14/05/12 16:44, hasufell wrote:
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
As can be judged by the title of my patches on the subject, I consider
-Werror to be short-sighted at best and idiotic at worst. The next GCC
version, which will
On 15.05.2012 13:29, Tony Chainsaw Vroon wrote:
On 14/05/12 16:44, hasufell wrote:
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
As can be judged by the title of my patches on the subject, I consider
-Werror to be short-sighted at best and
On Tuesday 15 May 2012 07:29:36 Tony Chainsaw Vroon wrote:
On 14/05/12 16:44, hasufell wrote:
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
As can be judged by the title of my patches on the subject, I consider
-Werror to be short-sighted
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
hasufell schrieb:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
-Werror is basically saying that it is
On Monday 14 May 2012 11:44:17 hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
the common
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
On 05/14/2012 06:13 PM, Alexandre Rostovtsev wrote:
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And
On Mon, 14 May 2012 18:01:22 +0200
Chí-Thanh Christopher Nguyễn chith...@gentoo.org 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
On Mon, 14 May 2012 17:44:17 +0200
hasufell hasuf...@gentoo.org wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
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 chith...@gentoo.org wrote:
-Werror is basically saying that it is not safe to ship code which
produces warnings.
An upstream demanding -Werror should work means
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/14/2012 06:03 PM, hasufell wrote:
On 05/14/2012 06:13 PM, Alexandre Rostovtsev wrote:
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in
Jeroen Roovers schrieb:
-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
13 matches
Mail list logo
