On Friday 21 July 2006 22:31, Kai Sattler wrote:
> Hi,
>
> Sorry, I could not answer directly to the former emails on this matter,
Which was because I didn't reply correctly.. I know better now. Sorry.

> because I was not subscribed to the list, therefore a separate email.  I
> I tried several configuration options to compile linuxwacom components
> under a monolythic kernel with the newest version linuxwacom-0.7.4-3,
> but without success. In the end I just tried to build the driver
> wacom_drv.o for Xorg-x11, and switch everything else off explicitly when
> calling configure:
>
> /configure --disable-wacom --disable-wacdump --disable-xidump
[...]
> so the build environment looks like:
[...]
> Shouldn't this be possible even with a monolythic kernel?
> However, the make process allways stops like this:
>
>
> make[3]: Leaving directory
> `/home/ksa/tmp/linuxwacom-0.7.4-3/src/wacomxi'
> Making all in 2.6.16
> make[3]: Entering directory
> `/home/ksa/tmp/linuxwacom-0.7.4-3/src/2.6.16'
>     Building linuxwacom drivers for 2.6 kernel.
> ***Note: Drivers not enabled as modules in your kernel config but
> requested through configure are NOT built
> make -C /usr/src/linux M=/home/ksa/tmp/linuxwacom-0.7.4-3/src/2.6.16
> make[4]: Entering directory `/usr/src/linux-2.6.16-gentoo-r7'
>
>   WARNING: Symbol version dump
> /usr/src/linux-2.6.16-gentoo-r7/Module.symvers
>            is missing; modules will have no dependencies and
> modversions.
>
>   Building modules, stage 2.
>   MODPOST
> /bin/sh: scripts/mod/modpost: No such file or directory
> make[5]: *** [__modpost] Error 127
> make[4]: *** [modules] Error 2
> make[4]: Leaving directory `/usr/src/linux-2.6.16-gentoo-r7'
> make[3]: *** [all] Error 2
> make[3]: Leaving directory `/home/ksa/tmp/linuxwacom-0.7.4-3/src/2.6.16'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/home/ksa/tmp/linuxwacom-0.7.4-3/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/ksa/tmp/linuxwacom-0.7.4-3'
> make: *** [all] Error 2
>
> I don't understand why the log still says "Drivers not enabled as
> modules in your kernel config but requested through configure are NOT
> built".

I agree.. Very confusing output.. I would guess there's a check missing if the 
kernel has module support or not when configure is run...

However, compiling the kernel modules are the last part of the make and should 
not affect the binaries that are usefull neither the wacom_drv.so (it should 
have been linked just before entering .../linuxwacom-0.7.4-3/src/wacomxi).

So, everything should be built and ready except that you can't 'make install' 
it.. Hmm...

What if you do something like the patch below does? I'm pretty sure you'll 
have to apply it manually, but what it should do is skipping the module 
compilation part. And then you should be able to 'make install' it. I'll try 
to make a patch of this which will do it the 'right' way in a few days.

--- linuxwacom-0.7.4-3/src/Makefile.orig        2006-07-22 00:02:06.000000000 
+0200
+++ linuxwacom-0.7.4-3/src/Makefile     2006-07-22 00:02:20.000000000 +0200
@@ -258,7 +258,7 @@ sbindir = ${exec_prefix}/sbin
 sharedstatedir = ${prefix}/com
 sysconfdir = ${prefix}/etc
 target_alias = 
-SUBDIRS = . wacomxi 2.6.16
+SUBDIRS = . wacomxi
 noinst_SCRIPTS =  wacom_drv.so
 lib_LTLIBRARIES = libwacomcfg.la
 wacomcfgdir = $(includedir)/wacomcfg

If you can't get the make to go through, it is always possible to copy the 
binaries to the right places by hand...

Hope this fix your compilation problems
 Magnus

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Linuxwacom-discuss mailing list
Linuxwacom-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

Reply via email to