Tclkit for Linux and Linux_64 version 8.5a2 has problems during startup when
running a Starkit. The 8.4.9 version of both work fine.
Here is the result with 8.5a2 (either standard or 64 bit):
mysystem:~/.../8.5a2> ./tclkit-linux-x86 clock.kit
application-specific initialization failed: couldn't read file "lib/tcl8.5/init.tcl":
no such file or directory
This requires a new TclKit release, see /tclkit/
while executing
"error $e"
invoked from within
"if {[catch { package require starkit; starkit::header mk4 -readonly }]} {
set e "This requires a new TclKit release, see /tclkit..."
(file "clock.kit" line 4)
I did verify that the vfs does contain the init.tcl file, but haven't dug any
deeper yet. Running Tclkit standalone appears to work fine and a Starkit can then
be sourced and will run properly.
Chuck (wcf3 on wiki)

After a bit of digging it appears to be a problem when the 'librarypath'
command is used during boot.tcl. After it is used the command 'info nameofexecutable'
returns an empty string.
If I simply comment out the resetting of the value 'noe' around line 54 of boot.tcl,
then the kit loads and runs properly. I'm not familier enough with why it is
being reset in order to know if this is a fix for the problem or not.
Chuck

Thanks for the bug report. I've applied your change to all tclkits in pub/tk/8.5a2/.