Juan, You shouldn't be running configure directly! Please read the README file for how to install AOLserver. If you run ./configure, this is the type of error you should expect.
tom jackson On Wednesday 09 April 2008 10:43, Juan José del Río (Simple Option) wrote: > Hello Tom, > > That's what i mean. The detection of the tclsh binary is what should be > fixed. The rest is all ok, so far I know. > > In my case, in FreeBSD, the tclsh isn't detected, which is not normal, > since I run ./configure --with-tcl=<path to my tcl> > > or am I wrong and it's broken for everyone? > > > The error is pretty annoying, and can prevent beginners from compiling > AOLServer from sources... which is not what we want, eh? > > > Regards, > > Juan José > > > > - > Juan José del Río | Comercio online / e-commerce > (+34) 616 512 340 | [EMAIL PROTECTED] > > > Simple Option S.L. > Tel: (+34) 951 930 122 > Fax: (+34) 951 930 122 > http://www.simpleoption.com > > On Wed, 2008-04-09 at 09:12 -0800, Tom Jackson wrote: > > Can we first identify the problem, then have someone who actually > > understands how it is supposed to work 'fix' it? It isn't broken, at > > least not in the way John thinks, or thought it was. > > > > Please look at nsconfig.tcl, and maybe even read the README file which > > has installation instructions. > > > > AOLserver should be installed using the tclsh identified in the configure > > option --with-tcl=... > > > > >From nsconfig.tcl: > > > > set tclsh [file native [info nameofexecutable]] > > set tcldir [file native [file dirname [file dirname $tclsh]]] > > set install $tcldir > > > > The script isn't perfect, it might need some work, but the other files > > are fine. > > > > >From the README: > > > > Unix: > > > > % /usr/local/aolserver/bin/tclsh84 ./nsconfig.tcl > > % gmake install > > > > The nsconfig.tcl script is designed to work on Unix and > > Windows. The tclsh used to execute the script must be from > > the installed Tcl location you intend to use for AOLserver > > as nsconfig.tcl will determine certain config settings from > > the tclsh environment. In addition, two options may be > > specified: > > > > -install dir Specify path to install (default: Tcl directory) > > -debug Debug build with symbols and without > > optimization.. > > > > On Windows, nsconfig.tcl will create include\ns.mak directly. > > > > On Unix, nsconfig.tcl will call the configure shell script > > with the appropriate options to create include/ns.mak. You > > may also run configure directly although it has few additional > > features. > > > > > > tom jackson > > > > On Wednesday 09 April 2008 09:34, Dossy Shiobara wrote: > > > On 2008.04.09, John Buckman <[EMAIL PROTECTED]> wrote: > > > > Can someone make this change in CVS: > > > > > > > > the utils/*.tcl files in CVS all need: > > > > > > > > #!/usr/local/bin/tclsh > > > > > > > > prepended at the top. Currently, they don't have this, and thus are > > > > run as shell scripts. > > > > > > > > They also need their permissions to be executable. > > > > > > > > I know we've switched to a tcl-building method, but "./configure" > > > > still (mostly) works, but more importantly, those util scripts are > > > > used by ns.mak and modules depend on them to work. > > > > > > If you execute configure with TCLSH=/usr/local/bin/tclsh, the scripts > > > will be executed correctly. > > > > > > If you hardcode a path to tclsh at the top of the scripts, it will only > > > work if others have their tclsh at that location. Not something you > > > can (safely) assume. > > > > > > > Dossy: if you are willing to give me cvs write privs, I can fix this. > > > > > > IMHO, the correct "fix" is to automatically detect (AC_PATH_TCLSH kind > > > of thing) in the autoconf _if_ TCLSH wasn't passed to configure. > > > > > > Would you mind doing that? I'd be happy to give you CVS write privs, > > > what's your SourceForge user ID? > > > > > > -- Dossy > > > > -- > > AOLserver - http://www.aolserver.com/ > > > > To Remove yourself from this list, simply send an email to > > <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the > > email message. You can leave the Subject: field of your email blank. > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the > email message. You can leave the Subject: field of your email blank. -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
