Hi,

Out of interest, does anyone know what rtnet needs Fortran for?

I gather its relation to fortran from the configure output.

Regards,

Roland

On 5/9/07, roland Tollenaar <[EMAIL PROTECTED]> wrote:
> Hi
>
> > Could you please show use the complete make output including command
> > line. rtdm_driver.h is in Xenomai's installation directory under
> > include/rtdm.
>
> This is the entire operation. I don't change any configure settings
> from what I understand there is no need for this.
>
> [EMAIL PROTECTED]:/usr/src/rtnet-0.9.9# ./configure
> checking build system type... i686-pc-linux
> checking host system type... i686-pc-linux
> checking for a BSD-compatible install... /usr/bin/ginstall -c
> checking for gcc... gcc
> checking for C compiler default output file name... a.out
> checking whether the C compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking for style of include used by make... GNU
> checking dependency style of gcc... gcc3
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking for a sed that does not truncate output... /usr/bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
> checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
> checking for /usr/i486-slackware-linux/bin/ld option to reload object
> files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking whether ln -s works... yes
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for f77... no
> checking for xlf... no
> checking for frt... no
> checking for pgf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for f90... no
> checking for xlf90... no
> checking for pgf90... no
> checking for epcf90... no
> checking for f95... no
> checking for fort... no
> checking for xlf95... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for gfortran... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether  accepts -g... no
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld)
> supports shared libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/i486-slackware-linux/bin/ld
> checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld)
> supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/i486-slackware-linux/bin/ld)
> supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> 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
>
> Kind regards,
>
> Roland Tollenaar
>
>
> >
> > 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