2.6.9-rc1-mm1 ppc build broken

[Albert Herranz]

Hi,

It seems that the waitid-system-call.patch in
2.6.9-rc1-mm1 introduced a circular include dependency
problem in the ppc arch.

The problem seems to be related to the addition of the
linux/resource.h header file in
include/asm-generic/siginfo.h for the new _rusage
field.

  CC      arch/ppc/kernel/asm-offsets.s
In file included from include/linux/mm.h:4,
                 from include/asm/io.h:7,
                 from include/linux/timex.h:61,
                 from include/linux/time.h:29,
                 from include/linux/resource.h:4,
                 from include/asm-generic/siginfo.h:6,
                 from include/asm/siginfo.h:4,
                 from include/linux/signal.h:7,
                 from
arch/ppc/kernel/asm-offsets.c:12:
include/linux/sched.h:276: error: field
`shared_pending' has incomplete type
include/linux/sched.h:379: error: parse error before
"sigval_t"
include/linux/sched.h:379: warning: no semicolon at
end of struct or union
include/linux/sched.h:386: error: parse error before
'}' token
include/linux/sched.h:534: error: `RLIM_NLIMITS'
undeclared here (not in a function)
include/linux/sched.h:554: error: field `pending' has
incomplete type
include/linux/sched.h:587: error: parse error before
"siginfo_t"
include/linux/sched.h:587: warning: no semicolon at
end of struct or union
include/linux/sched.h:607: error: parse error before
'}' token
include/linux/sched.h: In function `process_group':
include/linux/sched.h:611: error: dereferencing
pointer to incomplete type

Using gcc 3.3.2.
2.6.9-rc1, which does not include that patch, builds
fine for me.

Any others saw this?

Cheers,
Albert



		
______________________________________________
Renovamos el Correo Yahoo!: ¡100 MB GRATIS!
Nuevos servicios, más seguridad
http://correo.yahoo.es
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/