installazione driver USB

Riconoscimento, installazione e configurazione delle periferiche.
Scrivi risposta
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

installazione driver USB

Messaggio da spec3 »

ciao.
sto provando ad installare un driver usb che colleghi il mio pc a un dispositivo che un mio prof. mi ha dato(con driver annessi).
riporto l'errore che viene visualizzato seguendo la procedura di installazione (ho già fatto andare un file configure e ora do un comando make)

Codice: Seleziona tutto

gabriele@Paolo:~/work/mcc/libhid-0.2.12.orig$ make
make  all-recursive
make[1]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
Making all in hidparser
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/hidparser»
make[2]: Non c'è da fare nulla per «all»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/hidparser»
Making all in src
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
Making all in swig
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/swig»
if /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I..  -I/usr/include/python2.3/ -I../include -DHID_INTERNAL -DSWIG -I../include -I../hidparser -DNDEBUG -fPIC -fno-strict-aliasing -I/usr/local/include -O2 -Wall -W  -MT hid_wrap.lo -MD -MP -MF ".deps/hid_wrap.Tpo" -c -o hid_wrap.lo hid_wrap.c; \
        then mv -f ".deps/hid_wrap.Tpo" ".deps/hid_wrap.Plo"; else rm -f ".deps/hid_wrap.Tpo"; exit 1; fi
 gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/python2.3/ -I../include -DHID_INTERNAL -DSWIG -I../include -I../hidparser -DNDEBUG -fPIC -fno-strict-aliasing -I/usr/local/include -O2 -Wall -W -MT hid_wrap.lo -MD -MP -MF .deps/hid_wrap.Tpo -c hid_wrap.c  -fPIC -DPIC -o .libs/hid_wrap.o
hid_wrap.c:126:20: error: Python.h: No such file or directory
hid_wrap.c:757: error: expected ')' before '*' token
hid_wrap.c:781: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:807: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:861: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:882: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'SWIG_Python_AddErrorMsg':
hid_wrap.c:929: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:929: error: (Each undeclared identifier is reported only once
hid_wrap.c:929: error: for each function it appears in.)
hid_wrap.c:929: error: 'type' undeclared (first use in this function)
hid_wrap.c:930: error: 'value' undeclared (first use in this function)
hid_wrap.c:931: error: 'traceback' undeclared (first use in this function)
hid_wrap.c:933: warning: implicit declaration of function 'PyErr_Occurred'
hid_wrap.c:933: warning: implicit declaration of function 'PyErr_Fetch'
hid_wrap.c:936: error: 'old_str' undeclared (first use in this function)
hid_wrap.c:936: warning: implicit declaration of function 'PyObject_Str'
hid_wrap.c:937: warning: implicit declaration of function 'PyErr_Clear'
hid_wrap.c:938: warning: implicit declaration of function 'Py_XINCREF'
hid_wrap.c:940: warning: implicit declaration of function 'PyErr_Format'
hid_wrap.c:940: warning: implicit declaration of function 'SWIG_Python_str_AsChar'
hid_wrap.c:942: warning: implicit declaration of function 'Py_DECREF'
hid_wrap.c:945: warning: implicit declaration of function 'PyErr_SetString'
hid_wrap.c:945: error: 'PyExc_RuntimeError' undeclared (first use in this function)
hid_wrap.c: At top level:
hid_wrap.c:1050: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1125: error: expected ')' before '*' token
hid_wrap.c:1133: error: expected ')' before '*' token
hid_wrap.c:1144: error: expected ')' before '*' token
hid_wrap.c:1151: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1197: error: expected ')' before '*' token
hid_wrap.c:1299: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1310: error: expected specifier-qualifier-list before 'PyObject'
hid_wrap.c: In function 'SWIG_Python_CheckImplicit':
hid_wrap.c:1322: error: 'SwigPyClientData' has no member named 'implicitconv'
hid_wrap.c: At top level:
hid_wrap.c:1325: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1334: error: expected ')' before '*' token
hid_wrap.c: In function 'SwigPyClientData_Del':
hid_wrap.c:1389: warning: implicit declaration of function 'Py_XDECREF'
hid_wrap.c:1389: error: 'SwigPyClientData' has no member named 'newraw'
hid_wrap.c:1390: error: 'SwigPyClientData' has no member named 'newargs'
hid_wrap.c:1391: error: 'SwigPyClientData' has no member named 'destroy'
hid_wrap.c: At top level:
hid_wrap.c:1397: error: expected specifier-qualifier-list before 'PyObject_HEAD'
hid_wrap.c:1404: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1410: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1432: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1438: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1444: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1472: error: expected declaration specifiers or '...' before 'FILE'
hid_wrap.c: In function 'SwigPyObject_print':
hid_wrap.c:1478: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:1478: error: 'repr' undeclared (first use in this function)
hid_wrap.c:1478: warning: implicit declaration of function 'SwigPyObject_repr'
hid_wrap.c:1482: warning: implicit declaration of function 'fputs'
hid_wrap.c:1482: error: 'fp' undeclared (first use in this function)
hid_wrap.c: At top level:
hid_wrap.c:1491: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'SwigPyObject_compare':
hid_wrap.c:1502: error: 'SwigPyObject' has no member named 'ptr'
hid_wrap.c:1503: error: 'SwigPyObject' has no member named 'ptr'
hid_wrap.c: At top level:
hid_wrap.c:1508: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1525: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1527: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1534: error: expected ')' before '*' token
hid_wrap.c:1539: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1543: error: expected ')' before '*' token
hid_wrap.c:1577: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1594: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1610: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1622: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1634: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1682: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'swigobject_methods'
hid_wrap.c:1694: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1701: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1834: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1852: error: expected specifier-qualifier-list before 'PyObject_HEAD'
hid_wrap.c:1859: error: expected declaration specifiers or '...' before 'FILE'
hid_wrap.c: In function 'SwigPyPacked_print':
hid_wrap.c:1862: error: 'fp' undeclared (first use in this function)
hid_wrap.c:1863: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1863: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1867: error: 'SwigPyPacked' has no member named 'ty'
hid_wrap.c: At top level:
hid_wrap.c:1872: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1883: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'SwigPyPacked_compare':
hid_wrap.c:1897: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1898: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: warning: left-hand operand of comma expression has no effect
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: warning: left-hand operand of comma expression has no effect
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: warning: left-hand operand of comma expression has no effect
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: warning: left-hand operand of comma expression has no effect
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'pack'
hid_wrap.c:1900: error: 'SwigPyPacked' has no member named 'size'
hid_wrap.c: At top level:
hid_wrap.c:1903: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1905: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:1912: error: expected ')' before '*' token
hid_wrap.c:1918: error: expected ')' before '*' token
hid_wrap.c:1927: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2009: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2029: error: expected ')' before '*' token
hid_wrap.c:2045: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2051: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2066: error: expected ')' before '*' token
hid_wrap.c:2117: error: expected ')' before '*' token
hid_wrap.c:2132: error: expected ')' before '*' token
hid_wrap.c:2223: error: expected ')' before '*' token
hid_wrap.c:2255: error: expected ')' before '*' token
hid_wrap.c:2277: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2347: error: expected ')' before '*' token
hid_wrap.c:2368: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2386: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2407: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'SWIG_Python_GetModule':
hid_wrap.c:2428: warning: implicit declaration of function 'PyCObject_Import'
hid_wrap.c:2429: warning: assignment makes pointer from integer without a cast
hid_wrap.c: At top level:
hid_wrap.c:2443: error: expected ')' before '*' token
hid_wrap.c: In function 'SWIG_Python_DestroyModule':
hid_wrap.c:2484: warning: implicit declaration of function 'SWIG_This'
hid_wrap.c: In function 'SWIG_Python_SetModule':
hid_wrap.c:2489: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'swig_empty_runtime_method_table'
hid_wrap.c:2489: error: 'swig_empty_runtime_method_table' undeclared (first use in this function)
hid_wrap.c:2489: error: expected expression before ']' token
hid_wrap.c:2495: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:2495: error: 'module' undeclared (first use in this function)
hid_wrap.c:2495: warning: implicit declaration of function 'Py_InitModule'
hid_wrap.c:2498: error: 'pointer' undeclared (first use in this function)
hid_wrap.c:2498: warning: implicit declaration of function 'PyCObject_FromVoidPtr'
hid_wrap.c:2500: warning: implicit declaration of function 'PyModule_AddObject'
hid_wrap.c: At top level:
hid_wrap.c:2507: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'SWIG_Python_TypeQuery':
hid_wrap.c:2516: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:2516: error: 'cache' undeclared (first use in this function)
hid_wrap.c:2516: warning: implicit declaration of function 'SWIG_Python_TypeCache'
hid_wrap.c:2517: error: 'key' undeclared (first use in this function)
hid_wrap.c:2517: warning: implicit declaration of function 'SWIG_Python_str_FromChar'
hid_wrap.c:2518: error: 'obj' undeclared (first use in this function)
hid_wrap.c:2518: warning: implicit declaration of function 'PyDict_GetItem'
hid_wrap.c:2521: warning: implicit declaration of function 'PyCObject_AsVoidPtr'
hid_wrap.c:2527: warning: implicit declaration of function 'PyDict_SetItem'
hid_wrap.c: In function 'SWIG_Python_AddErrMesg':
hid_wrap.c:2546: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:2546: error: 'type' undeclared (first use in this function)
hid_wrap.c:2547: error: 'value' undeclared (first use in this function)
hid_wrap.c:2548: error: 'traceback' undeclared (first use in this function)
hid_wrap.c:2552: error: 'old_str' undeclared (first use in this function)
hid_wrap.c: In function 'SWIG_Python_ArgFail':
hid_wrap.c:2575: warning: implicit declaration of function 'snprintf'
hid_wrap.c:2575: warning: incompatible implicit declaration of built-in function 'snprintf'
hid_wrap.c: At top level:
hid_wrap.c:2583: error: expected ')' before '*' token
hid_wrap.c:2591: error: expected declaration specifiers or '...' before 'PyObject'
hid_wrap.c: In function 'SWIG_Python_TypeError':
hid_wrap.c:2605: error: 'obj' undeclared (first use in this function)
hid_wrap.c:2607: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:2607: error: 'str' undeclared (first use in this function)
hid_wrap.c:2610: error: 'PyExc_TypeError' undeclared (first use in this function)
hid_wrap.c: At top level:
hid_wrap.c:2630: error: expected ')' before '*' token
hid_wrap.c:2690:4: error: #error "This python version requires swig to be run with the '-classic' option"
hid_wrap.c:2721: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:2739: error: expected ')' before '*' token
hid_wrap.c: In function 'SWIG_CanCastAsInteger':
hid_wrap.c:2795: error: 'errno' undeclared (first use in this function)
hid_wrap.c:2795: error: 'EDOM' undeclared (first use in this function)
hid_wrap.c:2795: error: 'ERANGE' undeclared (first use in this function)
hid_wrap.c: At top level:
hid_wrap.c:2819: error: expected ')' before '*' token
hid_wrap.c:2858: error: expected ')' before '*' token
hid_wrap.c:2887: error: expected ')' before '*' token
hid_wrap.c:2963: error: expected ')' before '*' token
hid_wrap.c:2986: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3008: error: expected ')' before '*' token
hid_wrap.c:3052: error: expected ')' before '*' token
hid_wrap.c:3067: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3075: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3083: error: expected ')' before '*' token
hid_wrap.c:3098: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3110: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3140: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3162: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3192: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3214: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3244: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3266: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3297: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3325: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3355: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3377: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3407: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3429: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3442: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3463: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3470: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3500: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3522: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3552: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3574: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3603: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3625: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3653: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3675: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3705: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3727: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3740: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3761: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3768: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3789: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3810: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3831: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3844: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3865: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3886: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3899: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3912: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3925: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:3965: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4014: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4036: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4058: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4119: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4180: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4211: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4242: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'SwigMethods'
hid_wrap.c:4630: error: expected specifier-qualifier-list before 'PyObject'
hid_wrap.c:4636: error: expected specifier-qualifier-list before 'PyObject_HEAD'
hid_wrap.c:4640: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4649: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c: In function 'swig_varlink_print':
hid_wrap.c:4690: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:4690: error: 'str' undeclared (first use in this function)
hid_wrap.c:4690: warning: implicit declaration of function 'swig_varlink_str'
hid_wrap.c: In function 'swig_varlink_dealloc':
hid_wrap.c:4700: error: 'swig_varlinkobject' has no member named 'vars'
hid_wrap.c:4702: error: 'swig_globalvar' has no member named 'next'
hid_wrap.c: At top level:
hid_wrap.c:4709: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4727: error: expected declaration specifiers or '...' before 'PyObject'
hid_wrap.c: In function 'swig_varlink_setattr':
hid_wrap.c:4729: error: 'swig_varlinkobject' has no member named 'vars'
hid_wrap.c:4732: error: 'swig_globalvar' has no member named 'set_attr'
hid_wrap.c:4732: error: 'p' undeclared (first use in this function)
hid_wrap.c:4735: error: 'swig_globalvar' has no member named 'next'
hid_wrap.c:4738: error: 'PyExc_NameError' undeclared (first use in this function)
hid_wrap.c: At top level:
hid_wrap.c:4743: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4803: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4813: error: expected ')' before '*' token
hid_wrap.c:4829: error: expected '=', ',', ';', 'asm' or '__attribute__' before '*' token
hid_wrap.c:4842: error: expected ')' before '*' token
hid_wrap.c:4869: error: expected ')' before '*' token
hid_wrap.c: In function 'init_hid':
hid_wrap.c:4929: error: 'PyObject' undeclared (first use in this function)
hid_wrap.c:4929: error: 'm' undeclared (first use in this function)
hid_wrap.c:4929: error: 'd' undeclared (first use in this function)
hid_wrap.c:4929: warning: left-hand operand of comma expression has no effect
hid_wrap.c:4945: warning: implicit declaration of function 'SWIG_Python_FixMethods'
hid_wrap.c:4945: error: 'SwigMethods' undeclared (first use in this function)
hid_wrap.c:4952: warning: implicit declaration of function 'PyModule_GetDict'
hid_wrap.c:4955: warning: implicit declaration of function 'SWIG_Python_InstallConstants'
hid_wrap.c:4958: warning: implicit declaration of function 'SWIG_Python_SetConstant'
hid_wrap.c:4958: warning: implicit declaration of function 'SWIG_From_int'
make[2]: *** [hid_wrap.lo] Errore 1
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/swig»
make[1]: *** [all-recursive] Errore 1
make[1]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
make: *** [all] Errore 2
sembra che ci siano dei problemi nel trovare un header Python.h ma risultano già installati i pacchetti Python e Python-dev2.6 e quest'ultimo risulta al mio package manager come l'unico pacchetto contenente Python.h nei server di Ubuntu (i miei repositories sono settati per scaricare dai server italiani, attualmente ne vedo 4).

aggiungo che SWIG, il programma che c'entra con l'errore visualizzato, non era necessario installarlo ma mentre facevo girare il file configure erano apparsi due WARNING dicendomi che non avevo installati  ne SWIG ne DOXYGEN che  ho installato successivamente.

sapete darmi  una mano?
tra l'alltro facendo

Codice: Seleziona tutto

gabriele@Paolo:~$ locate Python.h
/usr/include/python2.6/Python.h
sembra che l'header incriminato ci sia...
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Potresti pubblicare il README o il file INSTALL (o entrambi) presenti probabilmente nella directory dei driver da compilare?
Hai verificato che tutte le dipendenze necessarie siano installate?
Che il compilatore non richieda determinati parametri?
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

readme

Codice: Seleziona tutto

libhid README
=============

libhid is (c) 2003-2005 by
  Martin F. Krafft <libhid@pobox.madduck.net>
  Charles Lepple <clepple+libhid@ghz.cc>
  Arnaud Quette <arnaud.quette@free.fr> && <arnaud.quette@mgeups.com>
and distributed under the terms of the GNU General Public License.
See the file ./COPYING in the source distribution for more information.

Revision: $Id: README 210 2005-02-20 21:14:40Z clepple $

Please send bugreports to <libhid-discuss@lists.ailab.ch>.

Introduction
------------

libhid is a rewrite of libHID[0] and aims to provide the same functionality
from a more organised framework. It aims to provide a layer of abstraction for
accessing HID-class devices over USB or serial lines (similar to what libusb
provides for the base USB protocol).

0. http://www.ghz.cc/~clepple/libHID/doc/html/

libhid has been designed because it is needed in two other projects
(libphdigets and nut). As such, it does not have a complete featureset yet but
is rather a work in progress (alpha state). We invite everyone to contribute
or get in touch with us for additional features.

Please find more information on the project website (once information becomes 
available):

  http://libhid.alioth.debian.org

You are welcome to sign up with the libhid mailing list at
  
  http://lists.ailab.ch/mailman/listinfo/libhid-discuss

for support.

Configuration
-------------

To configure the package, you will need the following software. In parentheses
are the versions used by the developers. Previous versions may work, but are
not supported. The names directly correspond to the Debian packages providing
the software.

  - libtool     (1.5.6-1)
  - automake1.8 (1.8.5-1)
  - autoconf    (2.59-7)
  - pkg-config  (0.15.0-4)
  - gcc         (3.3.4-2)

You should be able to use an earlier gcc 3.x compiler, or even a 2.x one (but
*please*, not 2.96). However, when experiencing compilation problems, please
upgrade your compiler.

On Debian systems, automake1.8 works as well as automake1.9. A slight problem
exists if automake1.4 is installed as it takes a higher priority than any
younger version in the alternatives system. If you can, purge that package,
it's trash. If, however, you need it, then you may want to consider pointing
/usr/bin/automake elsewhere:

  update-alternatives --set automake /usr/bin/automake-1.8

(or use -1.9). When you (finally) remove automake1.4, you can surrender
management back to the alternatives system:

  update-alternatives --auto automake

Make sure to check the version with `automake --version` before going on.

Furthermore, libhid needs libusb version 0.1.8beta or newer. It does not work
with libusb 1.0 at this moment. The following two Debian packages provide the
needed software:

  - libusb-0.1-4 (1:0.1.8-17)
  - libusb-dev (1:0.1.8-17)

If you want to build the swig python existension, you will need swig 1.3 
installed. The following two Debian packages provide it:

  - libswig1.3.22 (1.3.22-3)
  - swig (1.3.22-3)

To create man pages for the included utility programs, you need xsltproc and
the DocBook stylesheets.

  - xsltproc (1.1.12-5)
  - docbook-xsl (1.66.1-1)

Lastly, to compile the API documentation, you need doxygen, which is in the
following Debian package:

  - doxygen (1.2.15-2)

(Btw: pre-built Debian packages are available at
  http://people.debian.org/~madduck/packages/stage/libhid/binary/)

Once these are installed, the package can be configured and compiled.
Configuration happens as follows:

  $ ./autogen.sh [args]

where [args] is a space-separated list of the following:

  --prefix=/usr/local       installs the software under /usr/local
  --enable-debug            enables debugging symbols in the library
  --enable-maintainer-mode  enables automatic regeneration of configure and
                            Makefile scripts
  --disable-shared          only creates a library object for static
                            linking, which shortens compile time. generally,
                            this is not necessary.
More options are available. Consult the `./configure --help` output.

For most purposes, it suffices to issue the following command:
  
  $ ./autogen.sh --enable-debug

The recommended way to install the software (see below) requires you to
issue the following command:
  
  $ ./autogen.sh --enable-debug --prefix=/usr/local/stow/libhid

Following the configuration, the package can be build and installed as usual:

  $ make
  $ su           # if needed
  # make install

Help wanted
-----------

Note that the library is not (yet) complete and it's not thoroughly tested.
However, given the effort and grief we went through in writing it, we would
like to make it available to folks, get people to test it, and hopefully have
some peeps submit improvements. If you have any suggestions, please write to
us at libhid-discuss@lists.ailab.ch.

It's not yet documented, although the usage should be fairly straight
forward. We are hoping that someone steps forward and offers to document the
work. It generally results in better documentation, when it's not written by
the authors.

Furthermore, we are always looking for people willing to help out. In
particular, we would love to find someone willing to maintain the website.
We are also looking to rewrite the MGE HIDParser and implement new
functionality. If you are interested, please contact us at
libhid-discuss@lists.ailab.ch.

Credits
-------

The original library was written by Charles Lepple and Arnaud Quette. Martin
Krafft later joined and led the rewrite.

The library uses the HIDParser framework made available by MGE[1].

1. http://www.mgeups.com/opensource/projects/hidparser.htm

Usage
-----

The library supports pkg-config. Thus, to compile with the library,

  #include <hid.h>

and in your Makefile:

  CPPFLAGS += `pkg-config libhid --cflags`
  LDFLAGS += `pkg-config libhid --libs`

If using automake, use the AM_* versions of the two variables.

Have fun.
e INSTALL

Codice: Seleziona tutto

Installation Instructions
*************************

Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
Software Foundation, Inc.

This file is free documentation; the Free Software Foundation gives
unlimited permission to copy, distribute and modify it.

Basic Installation
==================

These are generic installation instructions.

   The `configure' shell script attempts to guess correct values for
various system-dependent variables used during compilation.  It uses
those values to create a `Makefile' in each directory of the package.
It may also create one or more `.h' files containing system-dependent
definitions.  Finally, it creates a shell script `config.status' that
you can run in the future to recreate the current configuration, and a
file `config.log' containing compiler output (useful mainly for
debugging `configure').

   It can also use an optional file (typically called `config.cache'
and enabled with `--cache-file=config.cache' or simply `-C') that saves
the results of its tests to speed up reconfiguring.  (Caching is
disabled by default to prevent problems with accidental use of stale
cache files.)

   If you need to do unusual things to compile the package, please try
to figure out how `configure' could check whether to do them, and mail
diffs or instructions to the address given in the `README' so they can
be considered for the next release.  If you are using the cache, and at
some point `config.cache' contains results you don't want to keep, you
may remove or edit it.

   The file `configure.ac' (or `configure.in') is used to create
`configure' by a program called `autoconf'.  You only need
`configure.ac' if you want to change it or regenerate `configure' using
a newer version of `autoconf'.

The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package.

  3. Optionally, type `make check' to run any self-tests that come with
     the package.

  4. Type `make install' to install the programs and any data files and
     documentation.

  5. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  To also remove the
     files that `configure' created (so you can compile the package for
     a different kind of computer), type `make distclean'.  There is
     also a `make maintainer-clean' target, but that is intended mainly
     for the package's developers.  If you use it, you may have to get
     all sorts of other programs in order to regenerate files that came
     with the distribution.

Compilers and Options
=====================

Some systems require unusual options for compilation or linking that the
`configure' script does not know about.  Run `./configure --help' for
details on some of the pertinent environment variables.

   You can give `configure' initial values for configuration parameters
by setting variables in the command line or in the environment.  Here
is an example:

     ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix

   *Note Defining Variables::, for more details.

Compiling For Multiple Architectures
====================================

You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory.  To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'.  `cd' to the
directory where you want the object files and executables to go and run
the `configure' script.  `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.

   If you have to use a `make' that does not support the `VPATH'
variable, you have to compile the package for one architecture at a
time in the source code directory.  After you have installed the
package for one architecture, use `make distclean' before reconfiguring
for another architecture.

Installation Names
==================

By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc.  You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PREFIX'.

   You can specify separate installation prefixes for
architecture-specific files and architecture-independent files.  If you
give `configure' the option `--exec-prefix=PREFIX', the package will
use PREFIX as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.

   In addition, if you use an unusual directory layout you can give
options like `--bindir=DIR' to specify different values for particular
kinds of files.  Run `configure --help' for a list of the directories
you can set and what kinds of files go in them.

   If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

Optional Features
=================

Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System).  The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.

   For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.

Specifying the System Type
==========================

There may be some features `configure' cannot figure out automatically,
but needs to determine by the type of machine the package will run on.
Usually, assuming the package is built to be run on the _same_
architectures, `configure' can figure that out, but if it prints a
message saying it cannot guess the machine type, give it the
`--build=TYPE' option.  TYPE can either be a short name for the system
type, such as `sun4', or a canonical name which has the form:

     CPU-COMPANY-SYSTEM

where SYSTEM can have one of these forms:

     OS KERNEL-OS

   See the file `config.sub' for the possible values of each field.  If
`config.sub' isn't included in this package, then this package doesn't
need to know the machine type.

   If you are _building_ compiler tools for cross-compiling, you should
use the `--target=TYPE' option to select the type of system they will
produce code for.

   If you want to _use_ a cross compiler, that generates code for a
platform different from the build platform, you should specify the
"host" platform (i.e., that on which the generated programs will
eventually be run) with `--host=TYPE'.

Sharing Defaults
================

If you want to set default values for `configure' scripts to share, you
can create a site shell script called `config.site' that gives default
values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists.  Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.

Defining Variables
==================

Variables not defined in a site shell script can be set in the
environment passed to `configure'.  However, some packages may run
configure again during the build, and the customized values of these
variables may be lost.  In order to avoid this problem, you should set
them in the `configure' command line, using `VAR=value'.  For example:

     ./configure CC=/usr/local2/bin/gcc

causes the specified `gcc' to be used as the C compiler (unless it is
overridden in the site shell script).  Here is a another example:

     /bin/bash ./configure CONFIG_SHELL=/bin/bash

Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
configuration-related scripts to be executed by `/bin/bash'.

`configure' Invocation
======================

`configure' recognizes the following options to control how it operates.

`--help'
`-h'
     Print a summary of the options to `configure', and exit.

`--version'
`-V'
     Print the version of Autoconf used to generate the `configure'
     script, and exit.

`--cache-file=FILE'
     Enable the cache: use and save the results of the tests in FILE,
     traditionally `config.cache'.  FILE defaults to `/dev/null' to
     disable caching.

`--config-cache'
`-C'
     Alias for `--cache-file=config.cache'.

`--quiet'
`--silent'
`-q'
     Do not print messages saying which checks are being made.  To
     suppress all normal output, redirect it to `/dev/null' (any error
     messages will still be shown).

`--srcdir=DIR'
     Look for the package's source code in directory DIR.  Usually
     `configure' can determine that directory automatically.

`configure' also accepts some other, not widely useful, options.  Run
`configure --help' for more details.

spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

ciao
del readme ho provato a fare il controllo e l'unica pacchetto che non trova è questo

Codice: Seleziona tutto

If you want to build the swig python existension, you will need swig 1.3 
installed. The following two Debian packages provide it:

  - libswig1.3.22 (1.3.22-3)
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

inoltre ho provato a cercarlo nei pacchetti di Debian (su www.debian.org) e con il package manager ma non trovo niente neanche che contenga il nome libswig...ultima nota: del readme al posto di automake1.8 avevo messo automake1.9...
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Non ne sono certo ma secondo me il problema dovrebbe derivare dalla libreria Python installata.
Dando un'occhiata all'otuput di "make" sembra infatti che questo vada a "frugare" nella directory "python2.3" che non trova perché tu hai installato la 2.6.
Potresti provare ad installare la 2.3 oppure creare ul link simbolico alla 2.6:

Codice: Seleziona tutto

sudo ln -s /usr/include/python2.6 /usr/include/python2.3
Ultima modifica di bingel il lunedì 16 agosto 2010, 15:13, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

ho provato il secondo.
ora l'errore che esce è sicuramente diverso:

Codice: Seleziona tutto

gabriele@Paolo:~/work/mcc/libhid-0.2.12.orig$ make
make  all-recursive
make[1]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
Making all in hidparser
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/hidparser»
make[2]: Non c'è da fare nulla per «all»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/hidparser»
Making all in src
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
Making all in swig
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/swig»
make[3]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[3]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/swig»
Making all in test
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/test»
make[3]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[3]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/src»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/test»
Making all in doc
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc»
Making all in www
make[3]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc/www»
make[3]: Non c'è da fare nulla per «all»
make[3]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc/www»
Making all in man
make[3]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc/man»
make[3]: Non c'è da fare nulla per «all»
make[3]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc/man»
make[3]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc»
chmod -R a+rX html
find html -type d -exec chmod 711 {} \;
make[3]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc»
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig/doc»
make[2]: ingresso nella directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
make[2]: *** Nessuna regola per creare l'obiettivo «debian/changelog», necessario a «all-am».  Arresto.
make[2]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
make[1]: *** [all-recursive] Errore 1
make[1]: uscita dalla directory «/home/gabriele/work/mcc/libhid-0.2.12.orig»
make: *** [all] Errore 2

Ultima modifica di spec3 il lunedì 16 agosto 2010, 15:29, modificato 1 volta in totale.
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Prima del comando make hai rieseguito configure?
Ultima modifica di bingel il lunedì 16 agosto 2010, 15:42, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

sì.
la prima volta che faccio andare il make compaiono anche degli warning in più ma credo sia normale...
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Per tagliare la testa al toro:

la libreria che stai tentando di compilare si trova già nei repo di ubuntu, prova ad installare i seguenti pacchetti:

Codice: Seleziona tutto

sudo apt-get install libhid-dev python-hid
Se tuttavia vuoi proprio compilare la tua versione, dopo aver comunque installato i pacchetti indicati, prova a rieseguire per l'ennesima volta configure e poi make.

Se non funziona neppure così prova ad installare la nuova versione della libreria scaricandola da qui:

https://alioth.debian.org/frs/download.php/1958/libhid-0.2.16.tar.gz

e quindi a compilarla. Da me (ubuntu 10.04) non ha dato problemi.
Ultima modifica di bingel il lunedì 16 agosto 2010, 16:34, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

allora...ho provato a installare i pacchetti ma nada...
ora provo a chiedere al mio prof. se c'è qualche controindicazione nell'installare la versione successiva...
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Due curiosità:

che versione di ubuntu hai installato?

che tipo di periferica devi collegare?

PS: se per la tua periferica può essere sufficiente (nel senso che la libreria non ti serve per compilare ulteriore software), puoi provare anche ad installare la libreria già compilata:

Codice: Seleziona tutto

sudo apt-get install libhid0
Si tratta della versione 0.2.15
Ultima modifica di bingel il lunedì 16 agosto 2010, 23:50, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

Kubuntu 10.4 LTS Lucid Lynx
è una centralina che converte il segnale elettrico in digitale (nel senso che le arriva un valore di corrente e in qualche modo, che capirò una volta installatola, ne acquisisce i valori di intensità)
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Ho appena aggiornato i mio precedente post. Vedi
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

ora aspetto la risposta di questo mio professore e vedo cosa fare(non credo ci siano problemi però visto che il materiale me lo ha dato lui non vorrei che voglia che usi proprio questo)...
cmq grazie mille per l'aiuto!
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Di nulla.
Probabilmente quei driver che ti ha dato richiedono una configurazione del sistema più vecchia per poter essere compilati. Considera che la versione 0.2.15 risale al 2006 (mi pare) pertanto di tempo ne è passato.
Secondo me non ci dovrebbero essere problemi di sorta, anzi, se la periferica funziona dovrebbe funzionare anche meglio visto che i driver di ubuntu sono più recenti.

Un'ultima cosa. Se la periferica è un dispositivo "Phidgets" prova ad installare anche quest'ulteriore libreria:

Codice: Seleziona tutto

sudo apt-get install libphidgets0
Saluti.
Ultima modifica di bingel il lunedì 16 agosto 2010, 23:50, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

Re: installazione driver USB

Messaggio da spec3 »

bingel ha scritto: Due curiosità:

che versione di ubuntu hai installato?

che tipo di periferica devi collegare?

PS: se per la tua periferica può essere sufficiente (nel senso che la libreria non ti serve per compilare ulteriore software), puoi provare anche ad installare la libreria già compilata:

Codice: Seleziona tutto

sudo apt-get instsall libhid0
Si tratta della versione 0.2.15
dopo questo comando mi dice: pronto per l'installazione manuale...come faccio ora?
Avatar utente
bingel
Imperturbabile Insigne
Imperturbabile Insigne
Messaggi: 4026
Iscrizione: lunedì 3 aprile 2006, 10:17

Re: installazione driver USB

Messaggio da bingel »

Credo perché probabilmente aveva già installato libhid0 quando ti ho fatto installare libhid-dev e python-dev.
Quindi in poche parole libhid0 dovrebbe essere già installato.
Per assicurartene:

Codice: Seleziona tutto

sudo dpkg-query -s libhid0 | grep Status
l'output dovrebbe essere:

Codice: Seleziona tutto

Status: install ok installed       #se installato
oppure

Codice: Seleziona tutto

Status: unknown ok not-installed   #se non installato

Se non fosse come dico o cmq ravvisassi ancora problemi e in ogni caso per tagliare nuovamente la testa al toro:

Codice: Seleziona tutto

sudo apt-get purge libhid-dev libhid0 python-dev libusb-dev
e poi reinstalli solo libhid0 ovvero solamente il file binario

Codice: Seleziona tutto

sudo apt-get install libhid0
Ultima modifica di bingel il lunedì 16 agosto 2010, 23:49, modificato 1 volta in totale.
Free Thought - Free World
spec3
Prode Principiante
Messaggi: 61
Iscrizione: lunedì 9 agosto 2010, 17:03

[Risolto] Re: installazione driver USB

Messaggio da spec3 »

alla fine il problema era che il mio prof. mi aveva dato dei driver difettati... >:(ora funge.
Scrivi risposta

Ritorna a “Driver e periferiche”

Chi c’è in linea

Visualizzano questa sezione: Bing [Bot] e 7 ospiti