Am 25.09.15 um 15:58 schrieb Zoran Vasiljevic:
> On 25 Sep 2015, at 15:44, Gustaf Neumann wrote:
>
>> kind of. the fix was addressing a problem in rivet under Linux,
>> the consequences were not easy to spot from the code but hit
>> all multi-threaded tcl applications, including NaviServer.
>> It
Hi all
The recompilation of naviserver 4.99.8 and modules did not seem to solve the
crashes
nsd: set.c:61: Ns_SetUpdate: Assertion `value != ((void *)0)' failed.
It now seems to crash more often.
However after days of extensive searching and going through ALL naviserver
settings i did find the t
On 25 Sep 2015, at 15:44, Gustaf Neumann wrote:
> kind of. the fix was addressing a problem in rivet under Linux,
> the consequences were not easy to spot from the code but hit
> all multi-threaded tcl applications, including NaviServer.
> It also lead to bug-reports from bsd about "massive slow
Am 25.09.15 um 14:46 schrieb Zoran Vasiljevic:
> On 25 Sep 2015, at 14:38, Gustaf Neumann wrote:
>
>> which will be fixed in 8.5.19, as well as the bug mentioned below (which can
>> cause problems for all kinds of forks, when e.g. nsproxy is not used for
>> "exec",
>> or for nscgi).
> Can it be t
On 25 Sep 2015, at 14:38, Gustaf Neumann wrote:
> which will be fixed in 8.5.19, as well as the bug mentioned below (which can
> cause problems for all kinds of forks, when e.g. nsproxy is not used for
> "exec",
> or for nscgi).
Can it be that somebody in Tcl was "too clever" and
short-sighte
I would not recommend using 8.5.18, using something in the range of
8.5.15 to 8.5.17
should be ok. We were hit not long ago by the following bug in Tcl 8.5.18
* http://core.tcl.tk/tcl/info/879a0747bee593e2
* http://core.tcl.tk/tcl/info/4b964e7afb811898
which will be fixed in 8.5.19, as well a
Dear Gustaf,
Thanks for the extra make flags, it now compiles successfully.
I never imagined 8.6 would be a culprit or that there could be so many
differences. But it's worth checking it out.
I'll give it a try locally to see if nothing breaks from downgrading to 8.6.
Although i'm sure i have to
Dear Andrei,
Thanks for the compile-log. The problem is that the compiler flags that are
picked up in your environment include a " -fvisibility=hidden", most likely
picked up from tcl 8.6.1. Using "-fvisibility=hidden" should work
certainly,
an was fixed in the tip versions.
The compilation w
Hi
I've tried compiling the 4.99.8 and I remembered why I even went to get the
bitbucket version, because of failure to compile.
Doing:./configure --prefix=/opt/ns --enable-symbols --enable-threads
make -j8 or simply 'make' Also trying with autoconf (maybe the configure missed
something?)This ho
Dear Gustaf,
many thanks for your help. The problem is solved. I have used tcl8.6-trunk and
it has
"-fvisibility=hidden" in its configure script. But later I realized that with
tcl8.6 naviserver has error messages at startup. With tcl8.5.11 the server is
working well.
Regards,
feri
Dear Ferenc,
The problem occurs during linking of nsthreadtest, which is a utility
for testing and not needed for the operations of naviserver.
Nevertheless, it should certainly work and it does work for me.
when i go to the directory naviserver/nsthread and issue there
rm *.o
rm n
Hello!
When I compile naviserver-4.99.4 the following error occures:
gcc -shared -O2 -fomit-frame-pointer -Wall -Wno-implicit-int -fPIC -pipe
-fvisibility=hidden -m64 -I../include -I"/home/feri/tanul/include"
-DHAVE_CONFIG_H -L../nsthread -L../nsd -L../nsdb -o libnsthread.so error.o
master
12 matches
Mail list logo