Andrej Kacian wrote:[Sun Jun 19 2005, 08:19:16PM EDT]
> I've been wondering - is there any eclass for fixing gcc warnings in $SUBJ
> for C/C++ source files?
Please don't do this. You're suggesting adding something to our tree
and ebuilds that will increase build time and hide upstream proble
Hi all,
I've been wondering - is there any eclass for fixing gcc warnings in $SUBJ
for C/C++ source files? I know it's upstream's job to fix these, and that they
have no effect on the compilation, but all there needs to be done is
'echo "" >> $file', and let's face it - it looks nicer when the co
