Hi,
I'm seeing these gcc warnings in test10-pre[23].
They could have occurred before that also -- I don't know.
I'm using gcc 2.7.2.3. Is that a problem?
Also, I can't boot test10-pre[23]. I get an oops in swapper.
It's not logged so I can't see where it's actually happening.
I'll try to hook up a serial connection so I can get the info.
Would any of the problems below keep me from being able
to boot?
sched.c:88: warning: alignment of `runqueue_lock' is greater than
maximum object file alignment
sched.c:89: warning: alignment of `tasklist_lock' is greater than
maximum object file alignment
sched.c:103: warning: alignment of `aligned_data' is greater than
maximum object file alignment
tcp_ipv4.c:78: warning: alignment of `tcp_hashinfo' is greater than
maximum object file alignment
socket.c:187: warning: alignment of `sockets_in_use' is greater than
maximum object file alignment
softirq.c:47: warning: section attribute ignored for uninitialized
variable `softirq_vec'
arch/i386/kernel/
irq.c:67: warning: alignment of `irq_desc' is greater than maximum
object file alignment
init_task.c:23: warning: alignment of `init_task_union' is greater than
maximum object file alignment
init_task.c:33: warning: alignment of `init_tss' is greater than maximum
object file alignment
misc.c:197: warning: type mismatch with previous external decl
../../../../lib/inflate.c:311: warning: previous external decl of
`memset'
misc.c:197: warning: type mismatch with previous implicit declaration
../../../../lib/inflate.c:311: warning: previous implicit declaration of
`memset'
misc.c:197: warning: `memset' was previously implicitly declared to
return `int'
Thanks,
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:09 EST