Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#67 nam version conflict for package "Tcl"

open
nobody
nam-1 (7)
5
2011-08-01
2011-08-01
Tom Henderson
No

nam version conflict for package "Tcl": have 8.5.10, need exactly 8.5.9

Reported here: http://mailman.isi.edu/pipermail/ns-developers/2011-July/009150.html

Discussion

  • Tom Henderson
    Tom Henderson
    2011-10-23

    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