Please test this and commit it if its ok. I run 2.6 and it doesn't look like this driver compiles there.
Created attachment 45988 [details] gpio-1.3.2.ebuild
didn't work: common_writelcd.c: At top level: common_writelcd.c:166: warning: type defaults to `int' in declaration of `EXPORT_NO_SYMBOLS' common_writelcd.c:166: warning: data definition has no type or storage class ld -r 4801driver.o 4501driver.o common_writelcd.o -o writelcd.o ++ echo 'writelcd(kernel/drivers:)' ++ sed -e 's:.*(\(.*\)):\1:' + module_temp=kernel/drivers: + modulename=writelcd + moduledir=kernel/drivers + moduledir=kernel/drivers + sourcedir= + sourcedir=/var/tmp/portage/gpio-1.3.2/work/gpio-1.3.2 + einfo 'Preparing writelcd module' + '[' no '!=' yes ']' + echo -e ' * Preparing writelcd module' * Preparing writelcd module + return 0 + cd /var/tmp/portage/gpio-1.3.2/work/gpio-1.3.2 + emake KERNELDIR=/usr/src/linux all make: Nothing to be done for `all'. + ARCH=x86 It created .o files but no .ko files and hence only installed empty directories. Ned is this 2.4 kernel only? Gotta run.
Yep 2.4.x only.
ok so linux-mod is no good for this 2.4.x based ebuild. linux-mod has a hard dep on module-init-tools which gpio has never been tested with as far as I know. Only virtual/modutils busybox is known to work.
just to update and reopen. Any hard deps on module-init-tools has gone. it should handle .o files just fine although of course, not if the target kernel is 2.6 This needs to fail if its trying to install into a 2.6 based kernel.
shoudla checked the ebuild first :)
