> > 2.4.19 with make allnoconfig produces these warnings.
> Just a hint:
> There is almost no software with completely clean code.
I can't agree. What you can say is that if you enable warnings
from the beginning, it's much easier because you prevent those
warnings, if you get them a couple of times.
If you upgrade your compiler, it can issue new warnings,
like you see when using gcc 3.x, or e.g. when changing from 2.8.x to
> Whenever you see one compiling and it produces no warnings it's most
> likely that the build script just suppresses warnings.
It can also mean that a software engineer has done a good job ;-)
Always look for -Wall as a start when using the gcc compiler.
> see you,
-- aYniK Software Solutions all You need is Knowledge Bedrijvenpark Twente 305 NL-7602 KL Almelo - the Netherlands P.O. box 134 NL-7600 AC Almelo - the Netherlands telephone: +31 (0)546-581400 fax: +31 (0)546-581401 a.marsman@aYniK.com http://www.aYniK.com
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/