Am Sonntag, den 06.01.2008, 19:44 +0100 schrieb Filippo Giunchedi:
> what is the status of this bug? Any change RTAI can be compiled with >=
> 2.6.18 ?
RTAI upstream has patches up to and including 2.6.24, so it's still a
matter of packaging all that sanely.
-Malte
--
To UNSUBSCRIBE, email
On Tue, 20 Mar 2007 19:10:46 -0700, Steve Langasek wrote:
> And the answer is, yes, the kernel-patch-adeos generated from the rtai
> source only supports kernels up to 2.6.8...
And besides, I tried to get 2.6.18 support [1] from upstream for etch, but
upstream does not care much [2] about 2.6.18
into account the 2.4.27 patch (since Debian sarge does not offer 2.4.26 etc
anymore).
Please test!
-Malte Cornils, from the BSP in Karlsruhe
diff -Naur rtai-3.1.0.orig/rtai-core/arch/i386/patches/hal16-2.4.27.patch rtai-3.1.0/rtai-core/arch/i386/patches/hal16-2.4.27.patch
--- rtai-3.1.0.orig/rtai
Hello,
try sticking an "#define EXPORT_SYMTAB 1" in fork.c, at the beginning of the
file.
It compiles for me after that.
Whether that is actually the correct solution remains to be determined.
BTW, for those trying to reproduce the bug, get kernel-package from unstable
(the version in sarge h
4 matches
Mail list logo