search

unixer / vtuner

Automatically exported from code.google.com/p/vtuner
0 stars 0 forks source link

Don't build with kernel 3.10 #33

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
make -C /root/openbricks/build/build.x86_64.eglibc/linux-3.10 
SUBDIRS=/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14
 modules
make[1]: Entering directory 
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_main.o
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_ctrldev.o
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_proxyfe.o
/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc
_main.c: In function 'vtunerc_init':
/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc
_main.c:345:4: error: implicit declaration of function 'create_proc_read_entry' 
[-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** 
[/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtuner
c_main.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** 
[_module_/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-1
4] Error 2
make[1]: Leaving directory 
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'
make: *** [default] Error 2

Original issue reported on code.google.com by pierluca...@gmail.com on 8 Jul 2013 at 1:29

GoogleCodeExporter commented 9 years ago 
Thanks for the report. 

It seems they removed the create_proc_read_entry() in 3.10 :-/

In the meantime you can compile the driver without CONFIG_PROC_FS defined 
(simplest way is to add an #undef CONFIG_PROC_FS to the vtunerc_prov.h)

/Honza

Original comment by jpetrous on 9 Jul 2013 at 7:29

GoogleCodeExporter commented 9 years ago 
I did very quick patch, unfortunatelly I can't check it right now on running 
kernel, so it can be broken in any way. 

If you want to check asap, please use the attached patchfile and report 
findings.

/Honza

Original comment by jpetrous on 9 Jul 2013 at 11:37

Attachments:

GoogleCodeExporter commented 9 years ago 
the patch is ok 
the build in ok

make -C /root/openbricks/build/build.x86_64.eglibc/linux-3.10 
SUBDIRS=/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14
 modules
make[1]: Entering directory 
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_main.o
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_ctrldev.o
  CC [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc_proxyfe.o
  LD [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.mod.o
  LD [M]  /usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/vtuner-driver-14/vtunerc.ko
make[1]: Leaving directory 
`/usr/local/src/openbricks.1.2/build/build.x86_64.eglibc/linux-3.10'

many tanks

i have modify the patch for version 1.4 of vtuner
these is the file

Original comment by pierluca...@gmail.com on 9 Jul 2013 at 12:31

Attachments: