I am installing a new system on an old Micron dual P90. I have
tried RedHat 5.0 (2.0.32 with glibc2) and SuSE 5.1 (2.0.33 without
glibc2), and seen the same thing on both installs.
When compiling the kernel, I will get undeclared variable
errors. They will be followed by parse errors, and the parse error will
always be of this type: "locks.c:790: parse error before character 0357"
Here is an example choke:
locks.c: In function `flock_lock_file':
locks.c:790: `err' undeclared (first use this function)
locks.c:790: (Each undeclared identifier is reported onlyonce
locks.c:790: for each function it appears in.)
locks.c:790: parse error before character 0357
make[2]: *** [locks.o] Error 1
The thing that really escapes me is this: if I take this bit of
code (which is line 790 from locks.c):
<tab><tab>error = -EAGAIN;
And replace it with this:
<15 spaces>error = -EAGAIN;
Locks.c will compile just fine. Things will go fine for a bit,
until I get my next "parse error before character 0357", and the same
fix will apply there also.
I'm probably just missing some basic point here (a cat -v does
not turn up anything odd in the source in question, though), but does
anyone have any idea what is going on? :) Why do two tabs choke gcc
when spaces do not? Isn't it all supposed to be leading whitespace?
Thanks for your thoughts-
--Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu