emerge -v fxload Calculating dependencies ...done! >>> emerge (1 of 1) sys-apps/fxload-20020411 to / >>> md5 src_uri ;-) fxload-2002_04_11.tar.gz >>> Unpacking source... >>> Unpacking fxload-2002_04_11.tar.gz to /var/tmp/portage/fxload-20020411/work >>> Source unpacked. gcc -c -O -Wall ezusb.c -o ezusb.o In file included from ezusb.c:33: /usr/include/linux/usbdevice_fs.h:49: error: variable or field `__user' declared void /usr/include/linux/usbdevice_fs.h:49: error: syntax error before '*' token /usr/include/linux/usbdevice_fs.h:56: error: variable or field `__user' declared void /usr/include/linux/usbdevice_fs.h:56: error: syntax error before '*' token /usr/include/linux/usbdevice_fs.h:100: error: variable or field `__user' declared void /usr/include/linux/usbdevice_fs.h:100: error: syntax error before '*' token /usr/include/linux/usbdevice_fs.h:109: error: syntax error before '}' token /usr/include/linux/usbdevice_fs.h:116: error: variable or field `__user' declared void /usr/include/linux/usbdevice_fs.h:116: error: syntax error before '*' token ezusb.c: In function `ctrl_msg': ezusb.c:123: error: storage size of `ctrl' isn't known ezusb.c:142: error: invalid application of `sizeof' to an incomplete type ezusb.c:142: error: invalid application of `sizeof' to an incomplete type ezusb.c:142: error: invalid application of `sizeof' to an incomplete type ezusb.c:142: error: invalid application of `sizeof' to an incomplete type ezusb.c:123: warning: unused variable `ctrl' make: *** [ezusb.o] Error 1 !!! ERROR: sys-apps/fxload-20020411 failed. !!! Function src_compile, Line 21, Exitcode 2 !!! (no error message) Reproducible: Always Steps to Reproduce: 1. 2. 3.
I'm guessing that you're using linux-headers-2.6.0 like me... Not sure what to do about this error, since usbdevice-fs.h appears to be an old and unmaintained header.
Created attachment 24422 [details, diff] fxload-2.6-headers.patch This trivial patch allows fxload to compile and run cleanly. I doubt it will work on a system with 2.4 headers and I don't know the best way of doing that kind of check in an ebuild, so I'll leave that up to someone else.
last linux26-headers should have this fixed
