Activity for next-scripting
-
next-scripting released /2.4.0/README
-
-
-
gustafn modified ticket #7
nsf does not work with Tcl/Tk 8.7.a5
-
Hi Paul, many thanks for the good report! This issues is fixed already in the tip version since May https://cvs.openacs.org/changelog/nsf?cs=e01e30551cfcc79872de5b8a08a31258e3414c97 the fixed release is ante portas All the best -g
-
Paul Obermeier created ticket #7
nsf does not work with Tcl/Tk 8.7.a5
-
Poor Yorick created ticket #6
:uplevel behaviour
-
-
-
-
ssoberni posted a comment on ticket #5
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
-
Zoran Vasiljevic posted a comment on ticket #5
I 'solved' the problem by scrapping all DTRACE variables from the Makefile and configure templates. Had to make awk script that does this for me automatically.
-
Here is the complete terminal output of configure/make: zoran@zoranvbox:~/hg/lexxapps/src/nsf2.2.0$ ./configure --enable-symbols --enable-threads --enable-64bit --with-tcl=/home/zoran/hg/lexxapps/src/tcl8.5.19/unix/ checking for correct TEA configuration... ok (TEA 3.10) configure: configuring nsf 2.2.0 Configuring NSF Version 2.2.0 checking for git... yes checking for Tcl configuration... found /home/zoran/hg/lexxapps/src/tcl8.5.19/unix/tclConfig.sh checking for gcc... gcc checking whether the C...
-
I have downloaded the fresh new 2.2.0 and there it works :-/ So SOMETHING is wrong between my older version of 2.2.0 and the new one. But I would like to know what, if possible. The only change is that my version was checked in under Mercurial as part of our project. I am afraid this will happen again so I would really like to find out what is happening. What files/info you need to be able to track this down?
-
FYI: I am using 8.5.19 Tcl
-
Dtrace and compile: again?
-
Cannot compile w/o dtrace
-
On Mon, 28 Jan 2019 11:44:51 +0100 Gustaf Neumann neumann@wu.ac.at wrote: maybe a leftover from an earlier "configure" with DTrace enabled. 2.2.0 is anyhow recommended and safe to use, it is more future proof, we use this as well in our live instances. yes, most probably something along those lines... right, nsf2.2.0 seems to be running fine.
-
On Fri, 25 Jan 2019 22:54:18 -0000 "ssoberni" foxcruiser@users.sourceforge.net wrote: 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 Interesting... I do not really know what is happening. After I switching...
-
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)...
-
I have downloaded the 2.2.0 and it compiles OK w.r.t missing dtrace. I guess I will then go to this release.
-
Cannot compile w/o dtrace
-
-
-
-
-
-
[current *] introspection does not fully honour ensemble methods
-
[current *] introspection does not fully honour ensemble methods
-
Next in ensemble call runs into unknown
-
Fix in commit 404b559
-
Ensemble dispatch via cmd resolver does not honour method combination (next)
-
[current *] introspection does not fully honour ensemble methods
-
Ensemble dispatch via cmd resolver does not honour method combination (next)
-
-
-
-
-
-
-
-
-
-
-
1
