On Sat, 30 Nov 2002, Rodolphe Ortalo wrote:
> > On Sat, 30 Nov 2002, Christoph Egger wrote: > > I just tried KGI, too. > [...] > > Please update from CVS again. > > Done. libgii built fine wrt kii/kgi now. Thanks. > > libggi compiled *nearly* fine, however, libggi configure.in does a > AC_CHECK_HEADER(kgi/kgi.h, ... ) in addition of the AC_TRY_COMPILE(..). > Apparently, AC_CHECK_HEADER ignores user-provided CFLAGS parameters for > gcc. In my case, '-I /usr/local/kgiwip/build/include', so it did not find > the header... I removed the AC_CHECK_HEADER test and kept only the > AC_TRY_COMPILE (the libgii way) and it ran... The ATI Mach64 > compilation failed (due to the HOST_OS and HOST_CPU issue - this one > really needs to be solved. I guess configure.in should define these macros > based on /bin/arch and /bin/uname results [1]) but the rest went fine. Yes, it needs to be solved. These defines are in kgi/config.h, which the kgi target for libggi doesn't seem to include consistently. In particular for the mach64 target, I think the #include <kgi/config.h> directive should be in libggi/include/ggi/display/kgi.h. I'll commit the fix. Note that to actually compile the mach64 target you'll need to copy the MACH64.h register definition file to the ggi tree. I still have to figure out how to properly share (build system wise) the file between kernel and userspace. > However, I also have problems with the man. :-) > > make[3]: *** No rule to make target `filter-key.7gii', needed by `all-am'. Stop. > make[2]: *** [all-recursive] Error 1 > make[1]: *** [all-recursive] Error 1 > make: *** [all-recursive-am] Error 2 Make sure you rerun autogen.sh due to recent change in building of manpages. -Filip
