Thus said "Joe Mistachkin" on Thu, 07 Aug 2014 21:14:56 -0700: > Yeah, it appears the "net change" was that Jim Tcl was updated. There > are quite a lot of changes to it since the last version. However, I > think it should be fine merging it to trunk? Any conflicting opinions?
No, looks fine now (as far as the merge is concerned). I tried to test it by making my /home unreadable (chmod 711 /home) but then Fossil couldn't even update, and all other kinds of problems happened: $ fossil up cannot find current working directory; Permission denied $ ./configure --disable-lineedit No installed jimsh or tclsh, building local bootstrap jimsh0 Runtime Error: stdlib.tcl:87: Failed to get pwd in procedure 'info nameofexecutable' called at file "./autosetup/test-tclsh", line 11 at file "stdlib.tcl", line 87 Runtime Error: stdlib.tcl:87: Failed to get pwd in procedure 'info nameofexecutable' called at file "./autosetup/test-tclsh", line 11 at file "stdlib.tcl", line 87 No working C compiler found. Tried cc and gcc. $ which tclsh /usr/local/bin/tclsh $ pwd /home/src/fossil $ cd /home $ pwd /home $ ls ls: .: Permission denied $ cd src $ ls fossil So clearly it's possible to navigate, but configure doesn't like it much. I tried with --debug and didn't get any other useful info. It's also odd that it didn't think it could find tclsh (yes I forgot to make tclsh disappear, but it thought it was gone already). Andy -- TAI64 timestamp: 4000000053e45372 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
