Patrick,
On Wed, Jan 07, 2004 at 05:21:38AM -0800, Patrick Samson wrote:
> Here is a description of how I succeeded to run a PL/Tcl script on
> Postgresql/Cygwin.
Thanks for finding a solution *and* your hard work! Would you be
willing to go the extra mile and submit patches to Insight (see below)
and PostgreSQL to finally put this one to bed?
> c. AppendDllPath(): would be the perfect solution, but is not yet
> adapted for cygwin standard (see
> http://cygwin.com/ml/cygwin/2004-01/msg00108.html)
If this is the best way to fix the problem, then I strongly encourage
you to go this route. What Chris was trying to tell you in his terse
response is the following:
If you have problems with this version of tcltk PLEASE SEND BUG
REPORTS TO THE INSIGHT MAILING LIST at "insight at sources dot
redhat dot com". Then the insight maintainers can help rectify
these issues. They are familiar with cygwin but, for obvious
reasons, should not be forced to read the cygwin mailing list to
find tcltk/insight problems.
Hence, you may get a better response if you send your Cygwin Tcl patch
to <insight at sources dot redhat dot com>.
> d. AppendEnvironment(): have to be THE solution, because there is no
> one else.
See above...
> 6. Add a call to Tcl_FindExecutable() in pltcl.c - pltcl_init_all(),
> just before the call to Tcl_CreateInterp().
Will this be obviated if Insight accepts your patch?
> 7. For the pltcl.dll to be built, I had to:
>
> a. Permute the order of tcl.h and postgres.h. See
> http://archives.postgresql.org/pgsql-bugs/2003-12/msg00184.php
>
> [Peter, Tom, I know you don't consider it as a definitive fix, but
> meanwhile it worked for me.]
The above is an ugly issue -- unfortunately, I don't know of a good
solution. :,(
Thanks,
Jason
--
PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers
Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6
