LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

RE:Problems with DAQ driver for Linux

Dear Sergey:

I work in the day but I can't still run the driver...

>>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<

El 10/25/00, 5:59:39 AM, Sergey Krasnishov
escribi� sobre el tema Re: Problems with DAQ driver for Linux:


> Ricardo,

> lnidaq is library where "ni" should be changed to "e".

The library that require the driver is the libnidaq.a, I change the
options to -ledaq to require libedaq.a but at
compile The driver send:

for i in driver lib tests; do cd "$i"; make; cd ..; done
make[1]: Entering directory `/usr/local/edaq/driver'
../niboards.pl
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c daq_driver.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c dio.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c ai.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c ao.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c gpct.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c misc.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c lowio.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c device_info.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c epromdac.c
gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
-fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c kal.c
ld -r -o edaq.o daq_driver.o dio.o ai.o ao.o gpct.o misc.o lowio.o
device_info.o epromdac.o kal.o
make[1]: Leaving directory `/usr/local/edaq/driver'
make[1]: Entering directory `/usr/local/edaq/lib'
gcc -Wall -Wstrict-prototypes -fPIC -c dio.c
gcc -Wall -Wstrict-prototypes -fPIC -c gpct.c
gcc -Wall -Wstrict-prototypes -fPIC -c ai.c
gcc -Wall -Wstrict-prototypes -fPIC -c ao.c
gcc -shared -o libedaq.so dio.o gpct.o ai.o ao.o
make[1]: Leaving directory `/usr/local/edaq/lib'
make[1]: Entering directory `/usr/local/edaq/tests'
cc -Wall -Wstrict-prototypes -O2 -I../driver testai.c -o testai
gcc -o testao -ledaq -Wall -Wstrict-prototypes -O2 -I../driver testao.o
-g
In file included from kal.c:351:
/usr/include/linux/bios32.h:11: warning: #warning This driver uses the
old PCI interface, please fix it (see Documentation/pci.txt)
ld: cannot find -ledaq
make[1]: *** [testao] Error 1 make[1]: Leaving directory
`/usr/local/edaq/tests'

I loocked for the library but I don't found it.

May be the problem is other. Can you tell me where can I find the
library?

This happens
> because of mistake in driver. They forget to change this from
previous
> version. You'll have to check names and change them this way. As far
as
> I remember it's somewhere in make and edaq driver config files.

> Don't forget to issue "make clean" before remaking files to avoid
> "nothing to be done" messages.

Thanks

> Configuration is not as simple with AT boards. You'll have to study
> isapnp.howto documents to understand process clearly. Check BIOS
setting
> for "not pnp OS" and adjust parameters for isapnp.conf in /etc
> directory. Check your isapnp tools for correct installation and
version
> see man pages and howto doc's. The experimental PC with this
> installation is not in my hands, so cannot send conf files to you
now.
> It was couple month before.

I read the man pages and I think that I have correctly configurated the
board.
If you have anything that can help me, please send me the
information...

Thank you

> Good luck,
> --
> Sergey Krasnishov
> ____________________________________
> Automated Control Systems
> National Instruments Alliance Member
> Moscow, Russia
> sergey_acs@levsha.ru
> http://acs.levsha.ru

> > Ricardo Leal Pacheco wrote:
> >
> > Dear Sergey:
> >
> > I reviewed the web page and change the kernel version an the gcc
> > version. I compile the driver and
> > I get the following:
> >
> > for i in driver lib tests; do cd "$i"; make; cd ..; done
> > make[1]: Entering directory `/usr/local/edaq-0.9.2/driver'
> > make[1]: Nothing to be done for `all'.
> > make[1]: Leaving directory `/usr/local/edaq-0.9.2/driver'
> > make[1]: Entering directory `/usr/local/edaq-0.9.2/lib'
> > make[1]: Nothing to be done for `all'.
> > make[1]: Leaving directory `/usr/local/edaq-0.9.2/lib'
> > make[1]: Entering directory `/usr/local/edaq-0.9.2/tests'
> > gcc -o testao -lnidaq -Wall -Wstrict-prototypes -O2 -I../driver
> > testao.o -g
> > make[1]: Leaving directory `/usr/local/edaq-0.9.2/tests'
> > ld: cannot find -lnidaq
> > make[1]: *** [testao] Error 1
> >
> > The board is ISA and I get some problems with the configuration. I
> > think that the problem is lnidaq library but
> > I don't know where I can get it.
> >
> > May be the compilation process had crashed and the next step of the
> > make don't finished succesfull
> >
> > Please, give some help for this problem.
> >
> > Thanks for your response...
> >
> > >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
> >
> > El 10/24/00, 3:33:12 PM, Sergey Krasnishov
> > escribi� sobre el tema Re: Problems with DAQ driver for Linux:
> >
> > > Take a look at the link below and around:
> > > http://www.ni.com/linux/daq_eseriesdl.htm
> > > Next Pay attention to kernel versioning issues in readme files.
There
> > is
> > > specific kernel dispatch interface in driver 😞
> >
> > > Your compiler has good version and should compile it.
> >
> > > About release dates ask NI about it, don't know. They promised
soon
> > 🙂
> >
> > > Cheers,
> > > --
> > > Sergey Krasnishov
> > > ____________________________________
> > > Automated Control Systems
> > > National Instruments Alliance Member
> > > Moscow, Russia
> > > sergey_acs@levsha.ru
> > > http://acs.levsha.ru
> >
> > > > Ricardo Leal Pacheco wrote:
> > > >
> > > > >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
> > > >
> > > > El 10/24/00, 8:09:12 AM, Sergey Krasnishov

> > > > escribi� sobre el tema Re: Problems with DAQ driver for Linux:
> > > >
> > > > > Are you using LOADLIN from Windows?
> > > >
> > > > No, when I use LV I boot from Linux directly without LOADLIN I
> > never
> > > > have used LOADLIN
> > > >
> > > > > It seems that your compiler and linux installation wrong for
this
> > > > > driver.
> > > >
> > > > > I have an experience of compiling this driver for kernel
2.2.x.
> > In
> > > > most
> > > > > cases it's compiled OK.
> > > >
> > > > > Most your errors coming from gcc compiler and kernel source
files
> > and
> > > > it
> > > > > seems that you should try to use normal linux and gcc
> > installation.
> > > > > Read instructions and try to check your gcc version "gcc -v"
and
> > > > compare
> > > > > it with recommended in doc's.
> > > >
> > > > I read doc's but I didn't find the recommended version. My
version
> > of
> > > > GCC is:
> > > >
> > > > gcc version 2.95.220000220(Debian GNU/Linux)
> > > >
> > > > Please tell me if It is the correct version and Where I will
find
> > the
> > > > recommended version.
> > > > May be I have a wrong release of the driver,
> > > >
> > > > > Note that this is beta driver and doesn't support DMA and
some
> > > > features
> > > > > in this version.
> > > >
> > > > > LabVIEW trials was failed for me, so if it's comercial
> > installation,
> > > > I'd
> > > > > recommend to wait before NIDAQ for linux will be released.
> > > >
> > > > When will be releases ?
> > > >
> > > > > --
> > > > > Sergey Krasnishov
> > > > > ____________________________________
> > > > > Automated Control Systems
> > > > > National Instruments Alliance Member
> > > > > Moscow, Russia
> > > > > sergey_acs@levsha.ru
> > > > > http://acs.levsha.ru
> > > >
> > > > > Ricardo Leal wrote:
> > > > > >
> > > > > > Hello:
> > > > > >
> > > > > > I need some help. I have a PC with Linux and Windows and I
want
> > to
> > > > use
> > > > > > an AT-MIO-16-DE DAQ board with LabVIEW for Linux,
Debian-2.2.
> > > > > > I downloaded de the edaq-0.9.2 of the web site but when I
> > compile
> > > > the
> > > > > > driver I get a lot of warning and errors after the make
> > command, a
> > > > part
> > > > > > of the list of errors is the following:
> > > > > >
> > > > > > lab-remoto1:/edaq-0.9.2# make
> > > > > > for i in driver lib tests; do cd "$i"; make; cd ..; done
> > > > > > make[1]: Entering directory `/edaq-0.9.2/driver'
> > > > > > gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> > > > > > -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c
> > daq_driver.c
> > > > > > In file included from daq_driver.c:3:
> > > > > > /usr/include/asm/signal.h:173: parse error before `size_t'
> > > > > > /usr/include/asm/signal.h:173: warning: no semicolon at end
of
> > > > struct or
> > > > > > union
> > > > > > /usr/include/asm/signal.h:174: warning: data definition has
no
> > type
> > > > or
> > > > > > storage class
> > > > > > In file included from /usr/include/linux/fs.h:262,
> > > > > > from /usr/include/linux/capability.h:13,
> > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > from /usr/include/linux/sched.h:8,
> > > > > > from daq_driver.c:4:
> > > > > > /usr/include/linux/hpfs_fs_i.h:5: parse error before
`ino_t'
> > > > > > /usr/include/linux/hpfs_fs_i.h:5: warning: no semicolon at
end
> > of
> > > > struct
> > > > > > or union
> > > > > > /usr/include/linux/hpfs_fs_i.h:12: parse error before `:'
> > > > > > In file included from /usr/include/linux/fs.h:264,
> > > > > > from /usr/include/linux/capability.h:13,
> > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > from /usr/include/linux/sched.h:8,
> > > > > > from daq_driver.c:4:
> > > > > > /usr/include/linux/msdos_fs_i.h:36: parse error before
`off_t'
> > > > > > /usr/include/linux/msdos_fs_i.h:36: warning: no semicolon
at
> > end of
> > > > > > struct or union
> > > > > > In file included from /usr/include/linux/fs.h:265,
> > > > > > from /usr/include/linux/capability.h:13,
> > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > from /usr/include/linux/sched.h:8,
> > > > > > from daq_driver.c:4:
> > > > > > /
> > > > > >
> > > > > > CAN SOMEONE HELP ME WITH THE INSTALLATION?--
> > Ricardo Leal Pacheco
> > E-mail: rleal@loa.alumnos.utfsm.cl / 7111100@entelpcs.cl
> > Universidad T�cnica Federico Santa Mar�a
> > Avda. Espa�a 1680
> > Valpara�so-CHILE
> > Tel.: (032)654622, Fax: (032)797656
0 Kudos
Message 1 of 2
(2,685 Views)
Ricardo,

I've found the latest one compiled successfully. Sending to you .tar
with original NI's sources and .zip with a compiled one version on my
PC.(in private mail only).
I hope that the name should be libedaq, not ledaq.

Try it.
--
Sergey Krasnishov
____________________________________
Automated Control Systems
National Instruments Alliance Member
Moscow, Russia
sergey_acs@levsha.ru
http://acs.levsha.ru

Ricardo Leal wrote:
>
> Dear Sergey:
>
> I work in the day but I can't still run the driver...
>
> >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
>
> El 10/25/00, 5:59:39 AM, Sergey Krasnishov
> escribi? sobre el tema Re: Problems with DAQ driver for Linux:
>
>
> > Ricardo,
>
> > lnidaq is library where "ni" should be changed to "e".
>
> The library that require the driver is the libnidaq.a, I change the
> options to -ledaq to require libedaq.a but at
> compile The driver send:
>
> for i in driver lib tests; do cd "$i"; make; cd ..; done
> make[1]: Entering directory `/usr/local/edaq/driver'
> ./niboards.pl
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c daq_driver.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c dio.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c ai.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c ao.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c gpct.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c misc.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c lowio.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c device_info.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c epromdac.c
> gcc -Wall -Wstrict-prototypes -pipe -O -fomit-frame-pointer
> -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c kal.c
> ld -r -o edaq.o daq_driver.o dio.o ai.o ao.o gpct.o misc.o lowio.o
> device_info.o epromdac.o kal.o
> make[1]: Leaving directory `/usr/local/edaq/driver'
> make[1]: Entering directory `/usr/local/edaq/lib'
> gcc -Wall -Wstrict-prototypes -fPIC -c dio.c
> gcc -Wall -Wstrict-prototypes -fPIC -c gpct.c
> gcc -Wall -Wstrict-prototypes -fPIC -c ai.c
> gcc -Wall -Wstrict-prototypes -fPIC -c ao.c
> gcc -shared -o libedaq.so dio.o gpct.o ai.o ao.o
> make[1]: Leaving directory `/usr/local/edaq/lib'
> make[1]: Entering directory `/usr/local/edaq/tests'
> cc -Wall -Wstrict-prototypes -O2 -I../driver testai.c -o testai
> gcc -o testao -ledaq -Wall -Wstrict-prototypes -O2 -I../driver
> testao.o
> -g
> In file included from kal.c:351:
> /usr/include/linux/bios32.h:11: warning: #warning This driver uses the
>
> old PCI interface, please fix it (see Documentation/pci.txt)
> ld: cannot find -ledaq
> make[1]: *** [testao] Error 1 make[1]: Leaving directory
> `/usr/local/edaq/tests'
>
> I loocked for the library but I don't found it.
>
> May be the problem is other. Can you tell me where can I find the
> library?
>
> This happens
> > because of mistake in driver. They forget to change this from
> previous
> > version. You'll have to check names and change them this way. As far
>
> as
> > I remember it's somewhere in make and edaq driver config files.
>
> > Don't forget to issue "make clean" before remaking files to avoid
> > "nothing to be done" messages.
>
> Thanks
>
> > Configuration is not as simple with AT boards. You'll have to study
> > isapnp.howto documents to understand process clearly. Check BIOS
> setting
> > for "not pnp OS" and adjust parameters for isapnp.conf in /etc
> > directory. Check your isapnp tools for correct installation and
> version
> > see man pages and howto doc's. The experimental PC with this
> > installation is not in my hands, so cannot send conf files to you
> now.
> > It was couple month before.
>
> I read the man pages and I think that I have correctly configurated
> the
> board.
> If you have anything that can help me, please send me the
> information...
>
> Thank you
>
> > Good luck,
> > --
> > Sergey Krasnishov
> > ____________________________________
> > Automated Control Systems
> > National Instruments Alliance Member
> > Moscow, Russia
> > sergey_acs@levsha.ru
> > http://acs.levsha.ru
>
> > > Ricardo Leal Pacheco wrote:
> > >
> > > Dear Sergey:
> > >
> > > I reviewed the web page and change the kernel version an the gcc
> > > version. I compile the driver and
> > > I get the following:
> > >
> > > for i in driver lib tests; do cd "$i"; make; cd ..; done
> > > make[1]: Entering directory `/usr/local/edaq-0.9.2/driver'
> > > make[1]: Nothing to be done for `all'.
> > > make[1]: Leaving directory `/usr/local/edaq-0.9.2/driver'
> > > make[1]: Entering directory `/usr/local/edaq-0.9.2/lib'
> > > make[1]: Nothing to be done for `all'.
> > > make[1]: Leaving directory `/usr/local/edaq-0.9.2/lib'
> > > make[1]: Entering directory `/usr/local/edaq-0.9.2/tests'
> > > gcc -o testao -lnidaq -Wall -Wstrict-prototypes -O2 -I../driver
> > > testao.o -g
> > > make[1]: Leaving directory `/usr/local/edaq-0.9.2/tests'
> > > ld: cannot find -lnidaq
> > > make[1]: *** [testao] Error 1
> > >
> > > The board is ISA and I get some problems with the configuration. I
>
> > > think that the problem is lnidaq library but
> > > I don't know where I can get it.
> > >
> > > May be the compilation process had crashed and the next step of
> the
> > > make don't finished succesfull
> > >
> > > Please, give some help for this problem.
> > >
> > > Thanks for your response...
> > >
> > > >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
> > >
> > > El 10/24/00, 3:33:12 PM, Sergey Krasnishov
> > > escribi? sobre el tema Re: Problems with DAQ driver for Linux:
> > >
> > > > Take a look at the link below and around:
> > > > http://www.ni.com/linux/daq_eseriesdl.htm
> > > > Next Pay attention to kernel versioning issues in readme files.
> There
> > > is
> > > > specific kernel dispatch interface in driver 😞
> > >
> > > > Your compiler has good version and should compile it.
> > >
> > > > About release dates ask NI about it, don't know. They promised
> soon
> > > 🙂
> > >
> > > > Cheers,
> > > > --
> > > > Sergey Krasnishov
> > > > ____________________________________
> > > > Automated Control Systems
> > > > National Instruments Alliance Member
> > > > Moscow, Russia
> > > > sergey_acs@levsha.ru
> > > > http://acs.levsha.ru
> > >
> > > > > Ricardo Leal Pacheco wrote:
> > > > >
> > > > > >>>>>>>>>>>>>>>>>> Mensaje original <<<<<<<<<<<<<<<<<<
> > > > >
> > > > > El 10/24/00, 8:09:12 AM, Sergey Krasnishov
>
> > > > > escribi? sobre el tema Re: Problems with DAQ driver for Linux:
>
> > > > >
> > > > > > Are you using LOADLIN from Windows?
> > > > >
> > > > > No, when I use LV I boot from Linux directly without LOADLIN I
>
> > > never
> > > > > have used LOADLIN
> > > > >
> > > > > > It seems that your compiler and linux installation wrong for
>
> this
> > > > > > driver.
> > > > >
> > > > > > I have an experience of compiling this driver for kernel
> 2.2.x.
> > > In
> > > > > most
> > > > > > cases it's compiled OK.
> > > > >
> > > > > > Most your errors coming from gcc compiler and kernel source
> files
> > > and
> > > > > it
> > > > > > seems that you should try to use normal linux and gcc
> > > installation.
> > > > > > Read instructions and try to check your gcc version "gcc -v"
>
> and
> > > > > compare
> > > > > > it with recommended in doc's.
> > > > >
> > > > > I read doc's but I didn't find the recommended version. My
> version
> > > of
> > > > > GCC is:
> > > > >
> > > > > gcc version 2.95.220000220(Debian GNU/Linux)
> > > > >
> > > > > Please tell me if It is the correct version and Where I will
> find
> > > the
> > > > > recommended version.
> > > > > May be I have a wrong release of the driver,
> > > > >
> > > > > > Note that this is beta driver and doesn't support DMA and
> some
> > > > > features
> > > > > > in this version.
> > > > >
> > > > > > LabVIEW trials was failed for me, so if it's comercial
> > > installation,
> > > > > I'd
> > > > > > recommend to wait before NIDAQ for linux will be released.
> > > > >
> > > > > When will be releases ?
> > > > >
> > > > > > --
> > > > > > Sergey Krasnishov
> > > > > > ____________________________________
> > > > > > Automated Control Systems
> > > > > > National Instruments Alliance Member
> > > > > > Moscow, Russia
> > > > > > sergey_acs@levsha.ru
> > > > > > http://acs.levsha.ru
> > > > >
> > > > > > Ricardo Leal wrote:
> > > > > > >
> > > > > > > Hello:
> > > > > > >
> > > > > > > I need some help. I have a PC with Linux and Windows and I
>
> want
> > > to
> > > > > use
> > > > > > > an AT-MIO-16-DE DAQ board with LabVIEW for Linux,
> Debian-2.2.
> > > > > > > I downloaded de the edaq-0.9.2 of the web site but when I
> > > compile
> > > > > the
> > > > > > > driver I get a lot of warning and errors after the make
> > > command, a
> > > > > part
> > > > > > > of the list of errors is the following:
> > > > > > >
> > > > > > > lab-remoto1:/edaq-0.9.2# make
> > > > > > > for i in driver lib tests; do cd "$i"; make; cd ..; done
> > > > > > > make[1]: Entering directory `/edaq-0.9.2/driver'
> > > > > > > gcc -Wall -Wstrict-prototypes -pipe -O
> -fomit-frame-pointer
> > > > > > > -fvolatile-global -DMODULE -D__KERNEL__ -DDAQ_DEBUG -c
> > > daq_driver.c
> > > > > > > In file included from daq_driver.c:3:
> > > > > > > /usr/include/asm/signal.h:173: parse error before `size_t'
>
> > > > > > > /usr/include/asm/signal.h:173: warning: no semicolon at
> end
> of
> > > > > struct or
> > > > > > > union
> > > > > > > /usr/include/asm/signal.h:174: warning: data definition
> has
> no
> > > type
> > > > > or
> > > > > > > storage class
> > > > > > > In file included from /usr/include/linux/fs.h:262,
> > > > > > > from /usr/include/linux/capability.h:13,
> > > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > > from /usr/include/linux/sched.h:8,
> > > > > > > from daq_driver.c:4:
> > > > > > > /usr/include/linux/hpfs_fs_i.h:5: parse error before
> `ino_t'
> > > > > > > /usr/include/linux/hpfs_fs_i.h:5: warning: no semicolon at
>
> end
> > > of
> > > > > struct
> > > > > > > or union
> > > > > > > /usr/include/linux/hpfs_fs_i.h:12: parse error before `:'
> > > > > > > In file included from /usr/include/linux/fs.h:264,
> > > > > > > from /usr/include/linux/capability.h:13,
> > > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > > from /usr/include/linux/sched.h:8,
> > > > > > > from daq_driver.c:4:
> > > > > > > /usr/include/linux/msdos_fs_i.h:36: parse error before
> `off_t'
> > > > > > > /usr/include/linux/msdos_fs_i.h:36: warning: no semicolon
> at
> > > end of
> > > > > > > struct or union
> > > > > > > In file included from /usr/include/linux/fs.h:265,
> > > > > > > from /usr/include/linux/capability.h:13,
> > > > > > > from /usr/include/linux/binfmts.h:5,
> > > > > > > from /usr/include/linux/sched.h:8,
> > > > > > > from daq_driver.c:4:
> > > > > > > /
> > > > > > >
> > > > > > > CAN SOMEONE HELP ME WITH THE INSTALLATION?--
> > > Ricardo Leal Pacheco
> > > E-mail: rleal@loa.alumnos.utfsm.cl / 7111100@entelpcs.cl
> > > Universidad T?cnica Federico Santa Mar?a
> > > Avda. Espa?a 1680
> > > Valpara?so-CHILE
> > > Tel.: (032)654622, Fax: (032)797656
0 Kudos
Message 2 of 2
(2,685 Views)