In a message dated 3/7/02 12:01:29 AM, [EMAIL PROTECTED] writes: >> That explains a few things.&-96; If the allocator modification is made to >> the Tcl core, will the AOLServer distribution be changed to link to the >> system Tcl lib's in a conventional manner?&-96; (eg, instead of including >> the modified? Tcl source and building from AOLServer's code tree). >> That would be very, *very* convenient. > >It is perfectably conceivably that that will happen, and we are >actually discussing this right now.&-96; It will mean keeping closer >communication between AOL and the core group for any changes that >are necessary, but that is likely all for the better anyway.
Hello, Yes - the goal is to eventually stop distributing our hacked version of Tcl. Some of the changes in AOLserver 4.0 were towards that goal, e.g., eliminating the nsthread library and the odd 7.6/8.x Tcl version dual build stuff. Now Jeff is actively working on the Tcl core side to eliminate the gap. Until the memory allocator stuff is cleared up, here's what I do to build with 8.4: 1. cvs co aolserver source in a directory, say src/aolserver 2. cvs co tcl into a different directory, say src/tcl. note this is the ordinary tcl source from the tcl sourceforge project, not from the aolserver sources 3. edit src/aolserver/include/Makefile.global to set version and directory 4. copy aolserver's hacked tcl8.3.4/generic/tclAlloc.c to tcl 8.4 source, e.g., src/tcl/generic/ 5. type make This should work for most platforms except OS/X which requires a bit more hacking still. -Jim
