Messages in this thread | | | Date | Tue, 14 Apr 1998 19:25:48 -0500 (CDT) | From | Mike Perry <> | Subject | Haunted system |
| |
line 116 of kmod.c from 2.1.96 is putting the hurt on gcc for some reason: kernel_thread(kmod_thread, NULL, CLONE_FILES | CLONE_FS | CLONE_SIGHAND);
For some reason, OR'ing any options to kernel_thread bugs out gcc in this fashion (only SOMETIMES!)
gcc-stable -D__KERNEL__ -I/usr/src/linux-2.1/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -pipe -fno-strength-reduce -m486 -malign-loops=2 -malign-jumps=2 -malign-functions=2 -DCPU=686 -c -o kmod.o kmod.c kmod.c: In function `kmod_init': kmod.c:117: parse error before character 0240 make[2]: *** [kmod.o] Error 1 make[2]: Leaving directory `/usr/src/linux-2.1/kernel' make[1]: *** [first_rule] Error 2 make[1]: Leaving directory `/usr/src/linux-2.1/kernel' make: *** [linuxsubdirs] Error 2
root:/usr/src/linux-2.1> gcc-stable -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.7.2.3/specs gcc version 2.7.2.3
Passing Two or more OR'ed paramaters (via defines, or constants) sometimes produces that error (sometimes not!) I have never seen gcc give a parse error in such a fashion..
Any ideas why this would happen? This occurrs in egcs 1.0.2 as well..
And as a side note: What the hell is this doing in my syslogs? Apr 14 19:17:37 mikepery -- MARK --
My system must be haunted..
--- Mike Perry Maintainer of www.linuxos.org and subpages.
"Make your Hardware work harder: Windows NT" -Microsoft ad for Windows NT ---
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |