I agree that the nsconfig.tcl script has limitations, with configure you have
to use the TCLSH option. Personally I always write a shell script to
memorialize the options I used, then I can copy the file around and edit it.
tom jackson
On Wednesday 09 April 2008 20:44, John Buckman wrote:
> >
On 2008.04.09, Tom Jackson <[EMAIL PROTECTED]> wrote:
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.
I wouldn't go so far as to say "you shouldn't run configure
dir
On Wednesday 09 April 2008 12:12, Dossy Shiobara wrote:
> % ./configure --with-tcl=... TCLSH=/path/to/your/tclsh
>
> I'd like to fix this so that autoconf picks up the TCLSH from the
> tclConfig.sh that's used by --with-tcl, possibly introduce --with-tclsh,
> if you want to compile against a pa
Exactly it is a problem, the problem is that they didn't read the README file,
although having an INSTALL file might help too. I make the same mistake as
John does, and come to the same conclusion he did until I remember what is
going on.
The configure script should error out with instructions
Tom Jackson wrote:
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
It may be a problem then that "everyone" knows when you see a configure
script
On 2008.04.09, Tom Jackson <[EMAIL PROTECTED]> wrote:
> 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.
I wouldn't go so far as to say "you shouldn't run configure dir
Juan,
Okay, one final note to pull all the suggestions and comments together:
1. No files need to be edited to add the #!... line
2. No files need to be executable.
3. Installation script is nsconfig.tcl which should be called by tclsh to be
used by AOLserver. This assumes that the home directo
Found the problem cause and the solution
Firing the following mysql command lets me get the right result from mysql
/*set character_set_results = NULL
*/That is after firing "use fresh" /*
** set sql1 "set character_set_results = NULL";
ns_db exec $db $sql1
*/
This is what mysql JDBC driv
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
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=
or am I wrong and it's broken for everyone?
The error is prett
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.
AO
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 t
Cite from http://wiki.tcl.tk/812:
There seems to be a growing consensus that the best way to
make a Tcl script executable as if it were a Bash or Sh script is to
put the following on the very top line of your Tcl (or Tk) script:
#!/usr/bin/env tclsh
well, the hack with the Tcl comment w
John Buckman wrote:
John Buckman schrieb:
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.
hmm, shouldn't this be a "/usr/bin/env tclsh" instead?
This looks to be the way it should be don
John, Everyone:
In case the message hasn't gotten through, there is nothing wrong with the tcl
scripts which don't have the exec bit set and don't have the shell code at
the top. Also ns.mak does not need to be updated.
tom jackson
On Wednesday 09 April 2008 08:15, John Buckman wrote:
> > Joh
John Buckman schrieb:
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.
hmm, shouldn't this be a "/usr/bin/env tclsh" instead?
This looks to be the way it should be done (from tests/new/al
Darren,
The Content-Type is set to *text/html; charset=utf-8*.
Though the way I have done is
/*ns_set put [ns_conn outputheaders] "Content-Type" "text/html;
charset=utf-8"
*/I tried the meta tag equivalent too but no luck!
/*
*/-- Rajesh Nair/*
*/
Darren Ferguson wrote:
I had similar issues
Hello John,
In include/ns.mak you can find a line with:
TCLSH =
just put there the path to your tclsh exec,
like /usr/local/bin/tclsh8.5-threads and you're done.
It'd be great if ./configure detected the available tclsh in your system
and write that line automa(g)ically.
Regards,
Juan Jos
I don't have the exact command here, but there is an install Tcl
(nsconfig.tcl) script which calls configure directly. This script is a little
screwed up and you can't pass in all the configure options you (or I want),
but the intent was that you do something like:
$ /path/to/my/aolserver/bin/t
On Wed, Apr 9, 2008 at 9:58 AM, John Buckman <[EMAIL PROTECTED]> wrote:
> Can someone make this change in CVS:
>
> the utils/*.tcl files in CVS all need:
>
> #!/usr/local/bin/tclsh
>
That seems non-portable. I don't run tcl out of /usr/local. Even
redhat el 5 has threaded tcl now.
Dave
> prep
John Buckman schrieb:
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.
hmm, shouldn't this be a "/usr/bin/env tclsh" instead?
-gustaf
--
AOLserver - http://www.aolserver.com/
To Remove y
Actually this is not what is needed, you need to use the tclsh for your
AOLserver installation, the tcl scripts are correct.
On Wednesday 09 April 2008 06:58, John Buckman wrote:
> Can someone make this change in CVS:
>
> the utils/*.tcl files in CVS all need:
>
> #!/usr/local/bin/tclsh
>
> prep
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, bu
I had similar issues and in the head component of my adp being generated
i had to add the following:
Once that was added the pages were rendered correctly.
Respectfully,
Darren Ferguson
Rajesh nair wrote:
Oops , forgot to attach the adp
-- Rajesh Nair
Rajesh Nair wrote:
Bas,
Apologies f
Oops , forgot to attach the adp
-- Rajesh Nair
Rajesh Nair wrote:
Bas,
Apologies for the delayed response!
Our setup is a complex set of components with a java component
inserting records
and tcl based RESTful service fetching the records back.
I have isolated this issue to a t
Bas,
Apologies for the delayed response!
Our setup is a complex set of components with a java component
inserting records
and tcl based RESTful service fetching the records back.
I have isolated this issue to a tcl script and am sending this out to
replicate the issue
1. My MySQL version i
On Tue, Apr 08, 2008 at 06:46:34PM -0700, Rick Cobb wrote:
> Tom, I'll take a small issue with your:
> > A
> > quick look at all the modules in CVS suggests that this is the best
> way to
> > contribute code, not by hacking on the core.
>
> I think that's an effect, not a cause. My company stop
27 matches
Mail list logo
