nsnam

I looked into this briefly. I think that the issue here is that tclcl,
when built, generates a file embedded-tcl.cc which includes some code from
init.tcl (e.g. "package require -exact Tcl 8.5.9") that is version
specific. This is enforced at runtime and prevents a user from separately
upgrading Tcl/Tk without upgrading ns-2 and nam-1. Some possible solutions
might be:
- hack the generation of embedded-tcl.cc along the lines in the post above
(not sure what side effects this has)
- investigate whether this package check is needed at all from init.tcl or
could be scrubbed altogether
- when packaging ns-2 and nam-1, do not use shared libraries from Tcl/Tk

Thread actually started here:
http://mailman.isi.edu/pipermail/ns-developers/2011-June/009141.html