ssoberni

Using 2.5.0, the output is: {:uplevel 0} 5 {:uplevel 1} 7 {:uplevel 2} 5 {:uplevel 3} 3 {uplevel 0} 7 {uplevel 1} 5 {uplevel 2} 3 So, uplevel seems good. :uplevel needs more thoughts, seems off by 1, here? @gneumann

Next in ensemble call runs into unknown

Fixed (tested with 2.5.0)

Dtrace and compile: again?

inactive for a long time, so closing

Hi Zoran! So SOMETHING is wrong between my older version of 2.2.0 and the new one. Could you zip up your 2.2.0 source directory and attach it to the ticket (or send it to us)? Pls make it sure it contains the artifacts of running a failing ./configure (config.log). I believe your DTRACE sensing code in configure is not working properly for some reason. This has certainly that smell. Can you tell me more about the build environment? Cheers, Stefan

Cannot compile w/o dtrace

Hi Zoran! Thanks for reporting! I tried to reproduce the reported issue. I got a fresh Ubuntu 18.10, installed the tcl and tcl-dev packages, obtained the nsf2.1.0.tar.gz tarball, unpacked it into a directory "nsf2.1.0". From therein: root@78ad7135e7eb:~/nsf2.1.0# ./configure root@78ad7135e7eb:~/nsf2.1.0# make root@78ad7135e7eb:~/nsf2.1.0# make test This yields: Regression Test Summary of NX+XOTcl: Environment: Tcl 8.6.8, OS Linux 4.9.125-linuxkit machine x86_64 threaded 1. NSF 2.1.0 (commit 2.1.0)...