| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi |
| 5 |
|
| 6 |
I'm using the ~x86 portage tree and emerge every new package as soon as it is |
| 7 |
available. |
| 8 |
Some times is watch gcc work and occasionally see some compiler warnings |
| 9 |
(unused variables, missing function definitions,...) |
| 10 |
|
| 11 |
- From my own little experience in C and C++ I know that a warning can turn into |
| 12 |
a full blown error sometimes. |
| 13 |
|
| 14 |
Would it be of any use to report the warnings to the developers or will they |
| 15 |
ignore it as they may have ignored them when compiling the software |
| 16 |
themselves? |
| 17 |
|
| 18 |
How should I report the warnings? Via bugs.gentoo.org or directly to the |
| 19 |
software developers? |
| 20 |
|
| 21 |
Is there an easy way to collect all warnings in a file when doing an 'emerge |
| 22 |
- -u world'? |
| 23 |
|
| 24 |
- -- |
| 25 |
|
| 26 |
|
| 27 |
|
| 28 |
~~~~~~~~~~~~~~~ |
| 29 |
|
| 30 |
Gerold Strobel |
| 31 |
~~~~~~~~~~~~~~~ |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.2.3 (GNU/Linux) |
| 34 |
|
| 35 |
iD8DBQE/3ITQeiAAHmcDbIERAhwDAKDf+nGcDp9DAIkW7VIbXdntwx14pgCfdwAR |
| 36 |
H71e1xZev/QzxFSYamwu4YI= |
| 37 |
=aq1L |
| 38 |
-----END PGP SIGNATURE----- |
| 39 |
|
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-dev@g.o mailing list |
Archives