On Thu, Aug 28, 2008 at 9:52 PM, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote:
>
> On 21.08.2008, at 21:06, Stephen Deasey wrote:
>
>> You used to have to manually edit the makefile to disable zippy. Is
>> this still the case?
>>
>> Perhaps the Tcl default should be to use the system allocator even o
On 21.08.2008, at 21:06, Stephen Deasey wrote:
> You used to have to manually edit the makefile to disable zippy. Is
> this still the case?
>
> Perhaps the Tcl default should be to use the system allocator even on
> threaded builds, and to provide a configure switch to enable zippy.
> Zoran, you
Thanks!
> ./configure --prefix=/usr --enable-threads --disable-64bit
>
> sed -i -e 's/-DUSE_THREAD_ALLOC=1//g' tclConfig.sh
> sed -i -e 's/-DUSE_THREAD_ALLOC=1//g' Makefile
-
This SF.Net email is sponsored by the Moblin Your
I mainly use Archlinux so i created package file but basically i added
just 2 lines to it and overall it looks like it:
./configure --prefix=/usr --enable-threads --disable-64bit
sed -i -e 's/-DUSE_THREAD_ALLOC=1//g' tclConfig.sh
sed -i -e 's/-DUSE_THREAD_ALLOC=1//g' Makefile
make install
Ber
> > You used to have to manually edit the makefile to disable zippy. Is
> > this still the case?
>
> What i do i use sed to replace zippy define after i ran configure, there
> is no easy way to disable it currently
Hi Vlad!
Can you share the way you do it? Thanks!
Bernd.
---
>
> You used to have to manually edit the makefile to disable zippy. Is
> this still the case?
>
What i do i use sed to replace zippy define after i ran configure, there
is no easy way to disable it currently
-
This SF.Net
On Thu, Aug 21, 2008 at 7:49 PM, Vasiljevic Zoran <[EMAIL PROTECTED]> wrote:
>
> On 21.08.2008, at 18:26, Vlad Seryakov wrote:
>
>> I always recompile Tcl with default memory
>> allocator: it has 2 benefits, 1) not-ever-growing, 2) i can use
>> vtmalloc
>> easily for example if default one does not
On 21.08.2008, at 18:26, Vlad Seryakov wrote:
> I always recompile Tcl with default memory
> allocator: it has 2 benefits, 1) not-ever-growing, 2) i can use
> vtmalloc
> easily for example if default one does not work like i need
yep. me too.
-
I think many issues or questions also are result of defaults in
Aolserver and Naviserver still being set according to past AOL setup and
requirements. It can be considered as an extreme case and because a lot
of functionality was implemented for AOL high-performance requirements
and setup, ever
Brett Schwarz wrote:
> Wow, I am amazed at the different reactions to this issue between
> this list and the aolserver list. Makes me want to switch to
> naviserver even more now...
90% of the difference is that the issue was introduced here by someone
saying "I contributed a patch." That in itse
ust 19, 2008 5:12:44 PM
Subject: Re: [naviserver-devel] Bug in fastpath cache causes info leak
I agree with this assessment. Nobody's fault in particular but
unfortunate circumstances. Still the fix is good and naviserver has
fastpath cache disabled as oppose to aolserver.
Stephen Deasey w
I agree with this assessment. Nobody's fault in particular but
unfortunate circumstances. Still the fix is good and naviserver has
fastpath cache disabled as oppose to aolserver.
Stephen Deasey wrote:
> fyi, there's talk of a bug in the fastpath cache on the aolserver
> list. I agree with the r
fyi, there's talk of a bug in the fastpath cache on the aolserver
list. I agree with the reporter, John: it's totally busted. I
committed a fix last night, but if you're not on the commits list you
won't have seen it. Heads up.
The fix was to lookup objects in the cache using the file name, as the
13 matches
Mail list logo
