-
Notifications
You must be signed in to change notification settings - Fork 62
Description
I was followin the steps in https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source making sure I wasn't missing something (other than updating dependencies just in case), and this follwing error is showing:
wacom_wac.c: In function ‘wacom_idleprox_timeout’:
wacom_wac.c:78:31: error: implicit declaration of function ‘from_timer’; did you mean ‘mod_timer’? [-Wimplicit-function-declaration]
78 | struct wacom *wacom = from_timer(wacom, list, idleprox_timer);
| ^~~~~~~~~~
| mod_timer
wacom_wac.c:78:55: error: ‘idleprox_timer’ undeclared (first use in this function)
78 | struct wacom *wacom = from_timer(wacom, list, idleprox_timer);
| ^~~~~~~~~~~~~~
wacom_wac.c:78:55: note: each undeclared identifier is reported only once for each function it appears in
make[6]: *** [/usr/lib/modules/6.17.7-arch1-1/build/scripts/Makefile.build:287: wacom_wac.o] Error 1
make[5]: *** [/usr/lib/modules/6.17.7-arch1-1/build/Makefile:2011: .] Error 2
make[4]: *** [/usr/lib/modules/6.17.7-arch1-1/build/Makefile:248: __sub-make] Error 2
make[4]: Leaving directory '/home/satoiji/Desktop/wacom/input-wacom-1.4.0/4.18'
make[3]: *** [Makefile:248: __sub-make] Error 2
make[3]: Leaving directory '/usr/lib/modules/6.17.7-arch1-1/build'
make[2]: *** [Makefile:43: all] Error 2
make[2]: Leaving directory '/home/satoiji/Desktop/wacom/input-wacom-1.4.0/4.18'
make[1]: *** [Makefile:365: all-recursive] Error 1
make[1]: Leaving directory '/home/satoiji/Desktop/wacom/input-wacom-1.4.0'
make: *** [Makefile:304: all] Error 2
…/Desktop/wacom ✗ make --v
GNU Make 4.4.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
tried with version 1.5 and 1.4 so far, both tar.gz and tar.bz2, making sure the autogen or configure weren't the issue, but seems it's persistent.