search

ShabbyX / RTAI

(NO LONGER MAINTAINED) Clone of RTAI from https://www.rtai.org
28 stars 17 forks source link

2.6 kernels broken #7

Closed NTULINUX closed 11 years ago

NTULINUX commented 11 years ago

Not sure how long this was broken, but it is now. Only tested on amd64 so far, almost certain this is broken for i386-i686 machines too. Help?

make all-recursive Making all in base Making all in include Making all in asm-x86 make[4]: Nothing to be done for all'. make[4]: Nothing to be done forall-am'. Making all in malloc make[3]: Nothing to be done for all'. Making all in sched Making all in liblxrt make[4]: Nothing to be done forall'. CC [M] /home/linuxcnc/RTAI/base/arch/x86/hal/hal.o In file included from /home/linuxcnc/RTAI/base/include/asm/rtai_hal.h:29:0, from /home/linuxcnc/RTAI/base/arch/x86/hal/hal.c:47: /home/linuxcnc/RTAI/base/include/asm/rtai_hal_64.h: In function 'rt_save_switch_to_real_time': /home/linuxcnc/RTAI/base/include/asm/rtai_hal_64.h:746:3: error: 'ipipe_root_status' undeclared (first use in this function) /home/linuxcnc/RTAI/base/include/asm/rtai_hal_64.h:746:3: note: each undeclared identifier is reported only once for each function it appears in /home/linuxcnc/RTAI/base/include/asm/rtai_hal_64.h:746:3: error: implicit declaration of function 'ipipe_set_current_domain' [-Werror=implicit-function-declaration] cc1: some warnings being treated as errors make[8]: * [/home/linuxcnc/RTAI/base/arch/x86/hal/hal.o] Error 1 make[7]: * [module/home/linuxcnc/RTAI/base/arch/x86/hal] Error 2 make[6]: * [rtai_hal.ko] Error 2 make[5]: * [rtai_hal.ko] Error 2 make[4]: * [rtai_sched.ko] Error 2 make[3]: * [all-recursive] Error 1 make[2]: * [all-recursive] Error 1 make[1]: * [all-recursive] Error 1 make: *\ [all] Error 2

NTULINUX commented 11 years ago

Looks kinda like this:

https://mail.rtai.org/pipermail/rtai/2013-February/025355.html

I think the merge of magma into master broke a few things, heh.

ShabbyX commented 11 years ago

@NTULINUX Yes, I knew this from a month ago:

http://mail.rtai.org/pipermail/rtai/2013-June/025590.html (and subsequent mails)

But since Paolo didn't give a single response, I thought we could just let it be. The fact is, even though we still use 2.6.38, that's a rather old kernel and it makes sense to say "last support for 2.6.38 was rtai 3.9".

The other thing about that is that the original ipipe patches (which Paolo (slightly) modifies for RTAI) changed their API greatly since the patch for kernel 3.2 (which I made work, but Paolo couldn't, so he dropped support for it). Anyway, given all that API change, I'm guessing it's too much of a trouble to both update RTAI to work with the new API and still support the old one. So it's fine if 2.6 is now broken (we just don't support it anymore).

I have a branch, "shabi-private" that is the snapshot of the repository just before you started working on it, which is basically "fixed" RTAI 3.9. If you want to install RTAI on 2.6, you can use it, but don't work on it. That's a branch not worth working on, but there just there for building on older systems.

NTULINUX commented 11 years ago

Ok, I'll delete the 2.x kernels then for x86 and x86_64 in master. Speaking of which I need to re-add 3.8.13 support

ShabbyX commented 11 years ago

... I need to re-add 3.8.13 support

Didn't you do that before?

NTULINUX commented 11 years ago

I did but I re-factored all the patches and deleted that one because half the patches weren't even applying, and my 3.8.13 kernel patch had a lot of fuzz in it.