Re: 2.6.32-rc4 fail compile -- drivers/char/rtc.c

From: Pete Clements
Date: Sun Oct 11 2009 - 22:34:18 EST


Quoting Xiaotian Feng
>
> This may be caused by commit d43c36dc6b357fa1806800f18aa30123c747a6d1.
> Can insert #include <linux/sched.h> into drivers/char/rtc.c fix this?

Yes, that clears the compile failure.

> On Mon, Oct 12, 2009 at 8:26 AM, Pete Clements
> <clem@xxxxxxxxxxxxxxxxxxxxx> wrote:
> > Fyi:
> > (i386 SMP)
> >
> >
> > =C2=A0CC =C2=A0 =C2=A0 =C2=A0drivers/char/rtc.o
> > drivers/char/rtc.c: In function 'rtc_interrupt':
> > drivers/char/rtc.c:271: error: 'TASK_INTERRUPTIBLE' undeclared (first use=
> in this function)
> > drivers/char/rtc.c:271: error: (Each undeclared identifier is reported on=
> ly once
> > drivers/char/rtc.c:271: error: for each function it appears in.)
> > drivers/char/rtc.c:273: error: 'SIGIO' undeclared (first use in this func=
> tion)
> > drivers/char/rtc.c:273: error: 'POLL_IN' undeclared (first use in this fu=
> nction)
> > drivers/char/rtc.c: In function 'rtc_read':
> > drivers/char/rtc.c:362: error: implicit declaration of function '__set_cu=
> rrent_state'
> > drivers/char/rtc.c:362: error: 'TASK_INTERRUPTIBLE' undeclared (first use=
> in this function)
> > drivers/char/rtc.c:376: error: implicit declaration of function 'signal_p=
> ending'
> > drivers/char/rtc.c:380: error: implicit declaration of function 'schedule=
> '
> > drivers/char/rtc.c:393: error: 'TASK_RUNNING' undeclared (first use in th=
> is function)
> > drivers/char/rtc.c: In function 'rtc_dropped_irq':
> > drivers/char/rtc.c:1206: error: 'TASK_INTERRUPTIBLE' undeclared (first us=
> e in this function)
> > drivers/char/rtc.c:1208: error: 'SIGIO' undeclared (first use in this fun=
> ction)
> > drivers/char/rtc.c:1208: error: 'POLL_IN' undeclared (first use in this f=
> unction)
> > make[2]: *** [drivers/char/rtc.o] Error 1
> > make[1]: *** [drivers/char] Error 2
> > make: *** [drivers] Error 2
> >
> > --
> > Pete Clements
--
Pete Clements
--
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/