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 idiotic at worst. The next GCC
> version, which will add *loads* of warnings to anything that compiled
> cleanly before, is going to kill you.
> Remove it from the build system. It is one of those patches that will
> probably live downstream until the end of time, but that is acceptable.

That's why IMHO the best way to fix those bugs is to make -Werror
optional. It the hardest path, but both upstream and downstream should
be satisfied.
Cheers,
Kacper

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 at best and idiotic at worst. The next GCC
> version, which will add *loads* of warnings to anything that compiled
> cleanly before, is going to kill you.

to clarify, having -Werror in upstream packages and getting enabled by default
when doing development is not short-sighted or idiotic at all, but in fact
makes a lot of sense for a lot of setups. shipping it enabled by default in a
release could be considered those things though.

a good compromise is what toolchain (and a few other) packages do: provide a
configure flag like --disable-werror.
-mike

On Mon, 14 May 2012 19:58:13 +0100
Markos Chandras <hwoarang@gentoo.org> wrote:

> On 05/14/2012 06:03 PM, hasufell wrote:
> > So, I will file a documentation bug unless someone can point me in
> > the right direction. I didn't find a reference to that issue.

> Open a bug, write a devmanual patch and I will be happy to apply it

FWIW I started a compiler flag policy / best-practice guide a while back.
One of these years I'll get around to actually writing it.


--
fonts, gcc-porting
toolchain, wxwidgets
@ gentoo.org

Ryan Hill posted on Mon, 25 Jun 2012 22:57:30 -0600 as excerpted:

> On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras <hwoarang@gentoo.org>
> wrote:
>
>> On 05/14/2012 06:03 PM, hasufell wrote:
>> > So, I will file a documentation bug unless someone can point me in
>> > the right direction. I didn't find a reference to that issue.
>
>> Open a bug, write a devmanual patch and I will be happy to apply it
>
> FWIW I started a compiler flag policy / best-practice guide a while
> back.
> One of these years I'll get around to actually writing it.

FWIW, flameeyes' blog has a lot of this sort of content, and with his
autotools mythbuster and similar content as well, I gather there's at
least some upstream eyes following it.

So that's a bit of a start for anyone looking for such information right
now, as well as reasonable research for anyone else considering writing
such a guide who might want some other references or quote-worthy
material.

I believe he has specifically covered -Werror too. I know he mentioned
it (with a link to /something/, of his or not I didn't check) in a recent
entry.

--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman

On 06/26/2012 06:59 AM, Duncan wrote:
> Ryan Hill posted on Mon, 25 Jun 2012 22:57:30 -0600 as excerpted:
>
>> On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras <hwoarang@gentoo.org>
>> wrote:
>>
>>> On 05/14/2012 06:03 PM, hasufell wrote:
>>>> So, I will file a documentation bug unless someone can point me in
>>>> the right direction. I didn't find a reference to that issue.
>>
>>> Open a bug, write a devmanual patch and I will be happy to apply it
>>
>> FWIW I started a compiler flag policy / best-practice guide a while
>> back.
>> One of these years I'll get around to actually writing it.
>
> FWIW, flameeyes' blog has a lot of this sort of content, and with his
> autotools mythbuster and similar content as well, I gather there's at
> least some upstream eyes following it.
>
> So that's a bit of a start for anyone looking for such information right
> now, as well as reasonable research for anyone else considering writing
> such a guide who might want some other references or quote-worthy
> material.
>
> I believe he has specifically covered -Werror too. I know he mentioned
> it (with a link to /something/, of his or not I didn't check) in a recent
> entry.
>

Then he should write it. +1 for that

On Tue, 26 Jun 2012 04:59:17 +0000 (UTC)
Duncan <1i5t5.duncan@cox.net> wrote:

> Ryan Hill posted on Mon, 25 Jun 2012 22:57:30 -0600 as excerpted:
>
> > On Mon, 14 May 2012 19:58:13 +0100 Markos Chandras
> > <hwoarang@gentoo.org> wrote:
> >
> >> On 05/14/2012 06:03 PM, hasufell wrote:
> >> > So, I will file a documentation bug unless someone can point me
> >> > in the right direction. I didn't find a reference to that issue.
> >
> >> Open a bug, write a devmanual patch and I will be happy to apply it
> >
> > FWIW I started a compiler flag policy / best-practice guide a while
> > back.
> > One of these years I'll get around to actually writing it.
>
> FWIW, flameeyes' blog has a lot of this sort of content, and with his
> autotools mythbuster and similar content as well, I gather there's at
> least some upstream eyes following it.

Thinking about it, it probably would be great to have some organized
catalog of flameeyes' posts. Or maybe he should write a book .

--
Best regards,
Michał Górny