symbolic link to hcitcl

[Bob Schmid]

why would symlink to hcitcl require sqlite3 ?

under Cloverleaf/cis6.1/integrator

symlink:

t6 -> /Cloverleaf/cis6.1/integrator/bin/hcitcl

from ksh> t6

application-specific initialization failed: can’t find package sqlite3 3.7

any ideas….

when I type in: hcitcl….

hcitcl> no problem

Topic

[Robert Kersemakers]

It looks like there is another ‘t6’ that gives the error. As you don’t specify a path, your search-path %PATH% is used and it apparently finds another t6.

Can you try

Code:

./t6

when you’re in /Cloverleaf/cis6.1/integrator. Or try

Code:

/Cloverleaf/cis6.1/integrator/t6

This should address the symlink and start hcitcl.

You can also try

Code:

which t6

It will search in %PATH% for ‘t6’.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Steve Carter]

Bob,

Did you ever get this resolved?  I’m running into the same issue and it just isn’t making any sense to me.

$ pwd

/appData/local/bin

$ ls -al hcitcl

lrwxrwxrwx    1 hci      prod             37 Aug 18 09:45 hcitcl -> /quovadx/cis6.1/integrator/bin/hcitcl

$ ./hcitcl

application-specific initialization failed: can’t find package sqlite3 3.7

hcitcl>exit

$ $HCIROOT/bin/hcitcl

hcitcl> “works just fine”

$ which hcitcl

/appData/local/bin/hcitcl

Thanks.

Steve

[Bob Schmid]

no I didnt

[Steve Carter]

That’s not what i wanted to hear.  🙁

Has anyone else run across an issue using a symbolic link to hcitcl in CIS6.1?  We’ve been using this for the past several verions without issue.  

Thanks.

Steve

[Scott Folley]

I don’t know that this is the answer but it may help you.

[Steve Carter]

Scott,

Thanks for the info.  I have a solution to avoid the use of the link, but Infor has indicated that it may be a bug in 6.1.1.  One of my developers identified the package require for clsqlite (replacement for gdbm) in $HCIROOT/tcl/libl/cloverleaf/init.tcl.  It references the sqlite3 package that you mentioned.  Everything works fine if I comment out that line.  Obviously that isn’t something that I want to do.  It would be nice to have it working as it was previously until I can fully implement the long-term solution.

I’ll post back to the forum when I have an answer from support/dev.

Thanks.

Steve

[Steve Carter]

Correction.  If I comment out the package require for clsqlite and use the symbolic link, a package require for sqlite will fail.

$HCIROOT/tcl/lib doesn’t contain a sqlite directory in 6.1.

At this point, until Infor supplies a patch, my best option is to change my scripts to use ‘/usr/bin/env tcl’ instead of the symbolic link.

Steve

[Charlie Bursell]

Steve:

! am a bit confused here.  I know it should work as you state but why do you need your own symbollic link to Tcl?  You are aware that tcl is already a symbollic link to hcitcl on Unix?  On Windows they are the same file.

I have always used /usr/bin/env tcl in my Unix scripts as it is more generic and the path does not have to change with each new Cloverleaf install.

Just curious/

[Russ Ross]

Now I think I understand what you are trying to accomplish.

I think you are looking for a method to make your stand alone TCL scripts not require a change when doing cloverleaf upgrades.

We are on cloverleaf 6.0 and I looked at our TCL standalone scripts and see we use the following

#!/usr/bin/env hcitcl

I’m curious if that errors in cloverleaf 6.1 since ours calls hcitcl instead of tcl.

Could you give that a try and let us know.

Russ Ross
RussRoss318@gmail.com

[Steve Carter]

Charlie,

At the time this was done, we didn’t realize the obvious.  Since it has worked for us for so many years, we just never looked to change.  I found a previous post of yours that recommended using ‘/usr/bin/env tcl’ and that’s the direction that we’re headed.

Russ – You are correct.  That was our goal many years ago.  ‘/usr/bin/env hcitcl’ also works.

Thank you both for the replies.

Steve

[Author]

Replies