| 1 |
On Sunday 14 December 2003 16:42, Gerold Strobel wrote: |
| 2 |
> From my own little experience in C and C++ I know that a warning can turn |
| 3 |
> into a full blown error sometimes. |
| 4 |
|
| 5 |
That depends very much on the nature of the cause, but it is true that in |
| 6 |
general warnings should be avoided. However many are caused by various |
| 7 |
compiler changes, so originally correct code may cause warnings. |
| 8 |
|
| 9 |
> Would it be of any use to report the warnings to the developers or will |
| 10 |
> they ignore it as they may have ignored them when compiling the software |
| 11 |
> themselves? |
| 12 |
|
| 13 |
I think that depends on the developers. However there are very many different |
| 14 |
compiler/glibc/arch/other dependency combinations so there is a good chance |
| 15 |
that what compiled clean for the developers doesn't for you. In that case |
| 16 |
they might want to see the warnings. |
| 17 |
|
| 18 |
> How should I report the warnings? Via bugs.gentoo.org or directly to the |
| 19 |
> software developers? |
| 20 |
|
| 21 |
Well, I don't think that many ebuild developers are even a bit interested in |
| 22 |
compiler warnings. |
| 23 |
|
| 24 |
Paul |
| 25 |
|
| 26 |
-- |
| 27 |
Paul de Vrieze |
| 28 |
Gentoo Developer |
| 29 |
Mail: pauldv@g.o |
| 30 |
Homepage: http://www.devrieze.net |
Archives