On Fri, 29 Nov 2002, Rodolphe Ortalo wrote:
> Hello, > > When trying to compile libggi & libgii (a CVS version from Wednesday IIRC) > --with-kii I have a few problems. > > Up to now, I've been obliged to apply a few fixes to "kii.h" (see diff) > and I'm wondering if there are correct. And as <kgi/system.h> > should be included by kii.h, I now have the following error: > > /bin/sh ../../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../input/kii >-I../.. -I../../../include -I../../include -I /usr/local/kgiwip/build/include >-D_REENTRANT -D_THREAD_SAFE -DDEBUG -g -Wall -c ../../../input/kii/input.c > gcc -DHAVE_CONFIG_H -I. -I../../../input/kii -I../.. -I../../../include >-I../../include -I /usr/local/kgiwip/build/include -D_REENTRANT -D_THREAD_SAFE >-DDEBUG -g -Wall -Wp,-MD,.deps/input.pp -c ../../../input/kii/input.c -fPIC -DPIC -o >input.lo > In file included from /usr/local/kgiwip/build/include/kii/kii.h:36, > from ../../../input/kii/input.c:33: > /usr/local/kgiwip/build/include/kgi/system.h:63: #error HOST_OS or HOST_CPU not >defined > /usr/local/kgiwip/build/include/kgi/system.h:100: #error check this, no type >definitions included? > /usr/local/kgiwip/build/include/kgi/system.h:112: #error kgi_udelay not implemented > /usr/local/kgiwip/build/include/kgi/system.h:120: #error kgi_nanosleep not >implemented > make: *** [input.lo] Error 1 > > However, it seems to me kgi/system.h is necessary for the > "KGI_SYS_DECLARE_INTEGRAL_TYPES(kii)"... I must be doing something wrong, > for sure. But well, what? Yes, Bernhard recently changed the headers so that the application has to include kgi/system.h before including kgi/kgi.h or kii/kii.h (I'm not really the expert on this so I can't give you reasons for this change). > Rodolphe > > PS: > > Concerning libggi, I get the following output (but well, it may be a > little early to worry due to the gii error): > > # /usr/local/bin/monitest > LibGG: unable to open lib: /usr/local/lib/ggi/input/kii.so: cannot open shared >object file: No such file or directory > LibGGI: failed to load input: kii > LibGGI: Failed to set mode: [P8/8] > unable to set any mode at all, exiting! > identified to mapper graphic-0.9.0-0 > Trying mode [] > Suggested mode [P8/8] > # > > and an error in kern.log: kgim_display_check_mode:401:E:Unknown command > fdeffff8 from monitor. Not bad! This means the ggi side seems to be working pretty well (except for the kii which should improve significantly once you're able to compile it :-) ). The unknown command from monitor is in fact an error message from the monitor driver (note to self: fix that silly meaningless error message) what that means is that the monitor driver doesn't like the mode you're trying to set. I'm not sure what monitest tries to do but you might want to try, say, stars as it doesn't use any specific mode and the default one then has a pretty good chance of working (the mode going to kgi is (0,0) which results in (640,400) being set if I'm not mistaken -- that should be useable with the current only useable monosync driver. I'm working on that, I'm hoping to have a real cool monitor driver soon). As to the patches, like I said, userspace now needs to include kgi/system.h before including kgi/kgi.h or kii/kii.h. As to the userspace portion of kii/kii.h declaring a bunch of functions to be used by userspace for interaction with kii, I'm pretty sure it should go altogether. Kernel has no bussiness specifying this kind of stuff especially since it is actually implemented in userspace (see libgii/input/kii/kii.c). It is my belief that Steffen put these function declarations there as a quick hack and they should go now. -Filip
