Jan Kiszka wrote:
Hans-Peter Bock schrieb:
AM_CPPFLAGS = \
-I$(top_srcdir)/include \
- -I$(top_builddir)/include
+ -I$(top_builddir)/include \
+ $(KERNEL_CFLAGS)
Well, generally it does not make sense to use kernel parameters for user mode tools. What kind of distribution are you using? Especially, where are your user mode includes from (/usr/include)? I guess your compilation fails because the IOCTL macro for user-kernel communication is not correct.
In general is doesn't, but for applications using ioctl it might be okay :-)
The KERNEL_CFLAGS variable only contains the path to the kernel source code include directory for which RTAI was configured and compiled. Since RTNet configures itself and works with a RTAI, it seemed logical to me that the RTAI Linux directory and the RTNet Linux directory were the same.
I do not compile and run Linux-ADEOS kernels on the same system, so using the local system directory (/usr/include/linux) is wrong in my case (in fact it's a 2.6 kernel that's running on my laptop).
It would be better if that specific makefile included $(LINUX_DIR) instead of $(KERNEL_CFLAGS) which would make clearer that it contained just the kernel location and no kernel compilation specific flags.
With friendly regards, Takis
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
