roland Tollenaar wrote:
> Hi,
> 
>> Maybe you should give the error messages for further help?
> 
> Absolutely. Here are the last few lines before configure bails out.
> 
> appending configuration tag "F77" to libtool
> checking for main in -lncurses... yes
> 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.
> 
> It tells me to check the rt extension installation which in my case is
> xenomai, which compiles and runs perfectly. rtdm is in the kernel
> source exactly where the xenomai patch puts it and rtnet -see above-
> knows that, and what version, xenomai is being used.

Could you please show use the complete make output including command 
line. rtdm_driver.h is in Xenomai's installation directory under 
include/rtdm. It gets installed with "make install".

Wolfgang.

> Kind regards,
> 
> Roland
> 
> 
>>
>> Am Dienstag, 8. Mai 2007 19:40 schrieb Roland Tollenaar:
>>> Hi,
>>>
>>> I am having problems building the rtnet package. For some reason my
>>> kernel src package does not seem compatible (2.6.16 and relatively
>>> standard AFAIK) to the configure script of rtnet.
>>>
>>> Trying to figure out what is going on in the configure script is no fun
>>> whatsoever. I am also pretty sure that unless there are more precise
>>> specification as to what the kernel src package must comply to in order
>>> for the beast to behave its of little use attempting to use rtnet.
>>> Because AFAIK and can see in the documentation there should be no problems.
>>>
>>> My current problem is that the configure script cannot find the
>>> rtdm_driver.h header in the kernel sources (but it is there, the
>>> configure script only seems to be looking in the wrong place).
>>>
>>> Am I supposed to feed the configure script some path as to where it must
>>> look? Does anyone know where it is looking so that maybe I can copy the
>>> rtdm_driver.h file to where it is looking?
>>>
>>> Or is there any manner to circumvent this configure script by simply
>>> getting the pre-compiled rtnet module somewhere?
>>>
>>> This is very frustrating.
>>>
>>> kind regards,
>>>
>>> Roland Tollenaar.
>> -------------------------------------------------------------------------
>> 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
>>
> 
> -------------------------------------------------------------------------
> 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
> 
> 


-------------------------------------------------------------------------
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

Reply via email to