--- Jim Davidson <[EMAIL PROTECTED]> wrote: > > 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 >
Hi Jim, Thanks for the information =) Just a few questions - I copied the AOLServer tclAolloc.c file to the tcl8.4 directory, did some creative Makefile hacking, and got a clean build linking against the "libtcl8.4.so" library. However, the resulting binary did not work - the server would randomly die, ocassionally logging messages such as "Tcl_SetStringObj called with shared object" to the server log. From this, I'm assuming that AOLServer does not play nicely with Tcl when dynamically linked? >From here, I tried building the binaries by linking against "libtclstub8.4.a". This gave me many many many many undefined reference errors, build failed. I'm using the SF Tcl source from CVS and the aolserver-3.4.2 source from the website. Any ideas as to what I might be doing wrong? thanks! thomas park __________________________________________________ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/
