---------- Forwarded message ---------- From: roland Tollenaar <[EMAIL PROTECTED]> Date: May 8, 2007 9:21 AM Subject: Re: Unsupported kernel version ? To: Jan Kiszka <[EMAIL PROTECTED]>
Hi, > Hmpf. Please make sure version.h looks like this: > > #define UTS_RELEASE "2.6.16" That helps. Any tip as to how I can use your echo instruction to achieve this? Would be convenient for my script...:) Anyhow the next show stopper is this. checking for RTnet Kconfig file... ./defconfig (default) checking for RT-extension... /lib/modules/2.6.16/build (kernel 2.6.16 + Xenomai) checking for Xenomai version... 2.3.1 checking for RTDM skin... y checking for RT-FireWire installation... none checking for RT-extension target arch... i386 checking for RTnet target arch... i386 checking for CROSS_COMPILE... none checking for kernel module extension... .ko checking for rtdm/rtdm_driver.h... no configure: error: *** header not found or working, please check RT-extension installation If someone could just point out where configure is looking because I have a relatively standard kernel-src package, it patches perfectly with xenomai and it is patched. How in hell can rtnet's configure not find the rtdm_driver.h header? Its right there! under /usr/src/linux-2.6.16/include/xenomai/rtdm_driver.h!! Appreciate any help here, thanks. Kind regards, Roland. On 5/6/07, Jan Kiszka <[EMAIL PROTECTED]> wrote: > roland Tollenaar wrote: > > Hi, > > > > The next show stopper is related to the same however. > > > > checking for RT-extension... /lib/modules/2.6.16/build (kernel #define > > UTS_RELEASE 2.6.16 + Xenomai) > > checking for Xenomai version... 2.3.1 > > checking for RTDM skin... y > > checking for RT-FireWire installation... none > > configure: error: *** Unsupported kernel version #define UTS_RELEASE 2.6.16 > > Hmpf. Please make sure version.h looks like this: > > #define UTS_RELEASE "2.6.16" > > i.e. that it is compilable C code. > > > > > it seems to be over-enthusiastically pulling out the entire line. > > > > I am using a distribution kernel I think but am not sure. I hope this > > is not a problem, for me having to work from a vanilla kernel as I > > believe they are called, would be really really problematic..... > > > > If we are going to hack, would it not be better to hack out the check > > for the kernel version out of the configure script? We know that the > > kernel version is correct so no need for configure to check that? If > > you agree, how would I turn this check off in configure? > > > > But we need a valid version number for a few compat wrappers. > > On the long term, this stuff (RTnet) should really be merged into > Xenomai, removing yet another entrance barrier for the users. Just takes > a bit time - and there's the problem again. :-> > > Jan > > > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
