Hey,
I get errors about the fastcall and type conflicts in 2.4.27
(yeah its old.. i know :) ) I was wondering what the politically
correct way of fixing these are? adding fastcall type to
kernel/sched.c or removing FASTCALL() around it in sched.h?
-DaMouse
--
I know I broke SOMETHING but its there fault for not fixing it before me
On Fri, 17 Sep 2004 18:38:46 +0100, DaMouse <[email protected]> wrote:
> I get errors about the fastcall and type conflicts in 2.4.27
>(yeah its old.. i know :) ) I was wondering what the politically
>correct way of fixing these are? adding fastcall type to
>kernel/sched.c or removing FASTCALL() around it in sched.h?
gcc-3.4? Known issue. Fixed in 2.4.28-pre ages ago,
as the LKML archives should have told you.
On Sat, 18 Sep 2004 00:23:42 +0200 (MEST), Mikael Pettersson
<[email protected]> wrote:
> On Fri, 17 Sep 2004 18:38:46 +0100, DaMouse <[email protected]> wrote:
> > I get errors about the fastcall and type conflicts in 2.4.27
> >(yeah its old.. i know :) ) I was wondering what the politically
> >correct way of fixing these are? adding fastcall type to
> >kernel/sched.c or removing FASTCALL() around it in sched.h?
>
> gcc-3.4? Known issue. Fixed in 2.4.28-pre ages ago,
> as the LKML archives should have told you.
>
Yeah, sorry i didn't think to look in 2.4.28-pre, thanks :)
-DaMouse
--
I know I broke SOMETHING but its there fault for not fixing it before me