Some versions of glibc define prinf as a macro instead of a function.
That is quite legal but it stops you using #ifdef inside printf calls.
I will change ksymoops to work around that.
>symbol.c:220:58: warning: trigraph ??> ignored
>symbol.c:221:44: warning: trigraph ??> ignored
>symbol.c:225:49: warning: trigraph ??> ignored
>symbol.c:226:35: warning: trigraph ??> ignored
I believe that is a gcc bug. The text is
options->hex ? "<END_OF_CODE+%llx/????>"
gcc is complaining about trigraphs but they are inside a string
constant, not in code. IMHO gcc should not flag trigraphs in string
constants, report it as a gcc bug.
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/