| 1 |
On Tuesday 15 May 2007 21:07:47 David Harel wrote: |
| 2 |
> Using kuroo, sometimes I get a notice such as: QA Notice: Package has |
| 3 |
> poor programming practices which may compile fine but exhibit random |
| 4 |
> runtime failures. Any idea what trigers such as message? |
| 5 |
|
| 6 |
It's not from kuroo. It's from portage. It's triggered by certain gcc warnings |
| 7 |
that portage is grepping for in /usr/lib/portage/bin/misc-function.sh. The |
| 8 |
intention is for people to file bugs about it (although you should try to |
| 9 |
avoid filing duplicates of existing bug reports). |
| 10 |
|
| 11 |
As Dan already mentioned there's a document about it in the portage trunk |
| 12 |
(although I'm not sure how to show it in a more readable format). The only |
| 13 |
related part from it he left out is: |
| 14 |
|
| 15 |
|| To fix this issue, use the methods proposed in the links mentioned earlier. |
| 16 |
|| If you're unable to do so, then a work around would be to append the gcc |
| 17 |
|| -fno-strict-aliasing flag to CFLAGS in the ebuild." |
| 18 |
|
| 19 |
Those are the existing bug reports with similar issues: |
| 20 |
|
| 21 |
http://tinyurl.com/2eer9q |
| 22 |
|
| 23 |
If you see it for a package not in that list you should thus file a bug.. |
| 24 |
|
| 25 |
-- |
| 26 |
Bo Andresen |
Archives