There was indeed a very old version of librep still hanging around (0.17). I:ve manually deleted as much of it as I could find, and also deleted the spurious gtk.a and types.a from /usr/lib64/rep/x86_64-unknown-linux-gnu/gui/gt k-2/ which were owned by no package.
I'm now getting a different compilation error when I try to build sawfish-1.6.3.1: make[2]: Entering directory `/root/rpmbuild/BUILD/sawfish-1.6.3.1/lisp/sawfish /gtk' REP_DL_LOAD_PATH=../../..//src/.libexec REP_GTK_DONT_INITIALIZE=1 REP_LOAD_PATH=../../../lisp:../../..//lisp rep compiler -f compile-batch stock.jl REP_DL_LOAD_PATH=../../..//src/.libexec REP_GTK_DONT_INITIALIZE=1 REP_LOAD_PATH=../../../lisp:../../..//lisp rep compiler -f compile-batch widget.jl error--> (file-error error--> "No such file or directory" "rep/lang/interpreter")( file-error "No such file or directory" "rep/lang/interpreter") I've downloaded and installed the rpm files provided by Kim Heino (thanks). I've also created a new user from scratch and window moving etc works with that user. However, the same error for compiling sawfish is occurring in both users if I try to run sawfish-config+ file-error "No such file or directory" "rep/lang/interpreter" So, there still seems to be a problem of some sort with librep (listing the installed files from the rpms comes up with only: /usr/lib64/rep/0.90.6/x86_64-unknown-linux-gnu/rep/vm/safe-interpreter.la /usr/lib64/rep/0.90.6/x86_64-unknown-linux-gnu/rep/vm/safe-interpreter.so /usr/share/rep/0.90.6/lisp/rep/lang/interpreter.jl /usr/share/rep/0.90.6/lisp/rep/lang/interpreter.jlc so there seem to be two problems. The first is figuring out what's messed up about my own username's settings which is preventing sawfish from working - I've tried removing my ~/.sawfish/custom but that makes no difference. The second is figuring out why sawfish-config can:t find the interpreter (and similarly why the compilation of sawfish fails - since sawfish isn's supported in a repository I:d like to be able to build my own versions of the latest releases in future). So, any ideas what gnome or sawfish or other settings might be causing the sawfish window management problem? That's the urgent question. -- Professor Andrew A Adams [email protected] Professor at Graduate School of Business Administration, and Deputy Director of the Centre for Business Information Ethics Meiji University, Tokyo, Japan http://www.a-cubed.info/
