ASTK Throws Error Msg. When Opened
- Claus
-
- Offline
- Moderator
-
Less
More
- Posts: 670
- Thank you received: 34
15 years 6 months ago #3568
by Claus
Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version
Replied by Claus on topic Re:ASTK Throws Error Msg. When Opened
Ah - you need to install 'tk' and 'tcl' - dependency checking should take care of the rest.
Then you should be able to run 'astk' manually and get (if any) an error report.
Then you should be able to run 'astk' manually and get (if any) an error report.
Code_Aster release : STA11.4 on OpenSUSE 12.3 64 bits - EDF/Intel version
- Steve Rednond
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 22
- Thank you received: 0
15 years 6 months ago #3570
by Steve Rednond
Replied by Steve Rednond on topic Re:ASTK Throws Error Msg. When Opened
Hi Claus,
Okay, I'll try that -- or actually, I already did last night, but unfortunately the Tcl/tk packages available for Puppy Linux are at version 8.5, not 8.4. So I tried creating symlinks labeled 8.4 to the 8.5 execuatables and libs. Probably I missed some, or that isn't a good idea. I basically got no response to atsk --help. So I removed all of the mods I had made, to try to think of a better way.
What confuses and surprises me is that Tcl/tk and wish8.4 are already included in the Salome-Meca binary package under prerequis/. Surely it was meant to be run from there? Does the postinstall script try to install them to /usr?
The astk script calling wish8.4 explicitly expects it to be in /usr/bin -- how would it get there? Salome Meca 4 is supposedly a binary package that is self-sufficient. That's partly why it is so big. It seems to contain Qt3, Tcl/tk and, I believe even Python. So why are scripts looking for executables in /usr? If these are needed, shouldn't the binary package come with a list of needed dependencies?
Well, anyway, I'll try to work around all this by manually copying the contents of the Salome Meca Tck/tk folder to the appropriate /usr locations.
I just have a feeling that something small is broken -- like some script method that tells astk to search its own prerequis directories for needed dependencies -- that would make it truly self-sufficient.
Any ideas about this?
Okay, I'll try that -- or actually, I already did last night, but unfortunately the Tcl/tk packages available for Puppy Linux are at version 8.5, not 8.4. So I tried creating symlinks labeled 8.4 to the 8.5 execuatables and libs. Probably I missed some, or that isn't a good idea. I basically got no response to atsk --help. So I removed all of the mods I had made, to try to think of a better way.
What confuses and surprises me is that Tcl/tk and wish8.4 are already included in the Salome-Meca binary package under prerequis/. Surely it was meant to be run from there? Does the postinstall script try to install them to /usr?
The astk script calling wish8.4 explicitly expects it to be in /usr/bin -- how would it get there? Salome Meca 4 is supposedly a binary package that is self-sufficient. That's partly why it is so big. It seems to contain Qt3, Tcl/tk and, I believe even Python. So why are scripts looking for executables in /usr? If these are needed, shouldn't the binary package come with a list of needed dependencies?
Well, anyway, I'll try to work around all this by manually copying the contents of the Salome Meca Tck/tk folder to the appropriate /usr locations.
I just have a feeling that something small is broken -- like some script method that tells astk to search its own prerequis directories for needed dependencies -- that would make it truly self-sufficient.
Any ideas about this?
- Steve Rednond
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 22
- Thank you received: 0
15 years 6 months ago #3571
by Steve Rednond
Replied by Steve Rednond on topic Re:ASTK Throws Error Msg. When Opened
Woohoo, getting somewhere.......
I temporarily added all the subdirectories of SALOME/SALOME4/Prerequis/ to the path via instructions found elsewhere on the internet:
I then ran ./astk but still got the missing /usr/bin/wish8.4 error message.
Looking more closely in my /usr/bin, I found I already had wish 8.5 there. So I edited the astk script to change 8.4 to 8.5 and all of a sudden, ./astk --help worked!
I'm looking at the results of ./astk --check now, and will report back what I find. I think we're close to a solution........
<br /><br />Post edited by: Steve Rednond, at: 2009/10/22 06:38

I temporarily added all the subdirectories of SALOME/SALOME4/Prerequis/ to the path via instructions found elsewhere on the internet:
DIRS=`echo /foo/bar/baz/*`
export PATH=$PATH:${DIRS// /:}
That adds subdirectories of /foo/bar/baz/ to the PATH environment variable
I then ran ./astk but still got the missing /usr/bin/wish8.4 error message.
Looking more closely in my /usr/bin, I found I already had wish 8.5 there. So I edited the astk script to change 8.4 to 8.5 and all of a sudden, ./astk --help worked!
I'm looking at the results of ./astk --check now, and will report back what I find. I think we're close to a solution........

- Steve Rednond
- Topic Author
- Offline
- Junior Member
-
Less
More
- Posts: 22
- Thank you received: 0
15 years 6 months ago #3572
by Steve Rednond
Replied by Steve Rednond on topic Re:ASTK Throws Error Msg. When Opened
astk --check was reporting that it couldn't find .astkrc_salome2009.1/config_serveurs and prefs.
When I checked, the folder and files were in fact there, but config_serveurs was an empty text file and prefs had _VIDE in practically all entries. I also found that rsh and rcp executables were missing from my computer.
I decided to leave Puppy Linux 4.1.2 and boot into Ubuntu, and install Salome Meca there to see if I could get it to run on a different OS.
After a false start in Ubuntu, when the program crashed immediately, I downloaded proprietary NVIDIA restricted drivers and enabled them. Salome Meca worked well then, and I was able to get astk running -- First time I had seen the interface!!
I then looked at the config_serveurs and prefs there and was able to see what they should look like on a working installation. I also looked at the hosts file.
Then I rebooted into Puppy Linux, installed rcp and rsh, made a slight modification to the Hosts file, copied the working config-serveurs and prefs files from Ubuntu to Puppy, and modified them to suit the new environment -- mostly changed the terminal program and editors.
I rebooted, ran Salome Meca, and SUCCESS!! I was able to get the astk interface running.
ps. I also created a symlink in usr/bin between wish8.4 and 8.5. I haven't had to set the path for the prerequis directory since then, so that seems to be the only change needed there,
Thanks to all who helped -- I couldn't have got through this without the suggestions for where to look.
--Steve<br /><br />Post edited by: Steve Rednond, at: 2009/10/22 06:46
When I checked, the folder and files were in fact there, but config_serveurs was an empty text file and prefs had _VIDE in practically all entries. I also found that rsh and rcp executables were missing from my computer.
I decided to leave Puppy Linux 4.1.2 and boot into Ubuntu, and install Salome Meca there to see if I could get it to run on a different OS.
After a false start in Ubuntu, when the program crashed immediately, I downloaded proprietary NVIDIA restricted drivers and enabled them. Salome Meca worked well then, and I was able to get astk running -- First time I had seen the interface!!

I then looked at the config_serveurs and prefs there and was able to see what they should look like on a working installation. I also looked at the hosts file.
Then I rebooted into Puppy Linux, installed rcp and rsh, made a slight modification to the Hosts file, copied the working config-serveurs and prefs files from Ubuntu to Puppy, and modified them to suit the new environment -- mostly changed the terminal program and editors.
I rebooted, ran Salome Meca, and SUCCESS!! I was able to get the astk interface running.

ps. I also created a symlink in usr/bin between wish8.4 and 8.5. I haven't had to set the path for the prerequis directory since then, so that seems to be the only change needed there,
Thanks to all who helped -- I couldn't have got through this without the suggestions for where to look.
--Steve<br /><br />Post edited by: Steve Rednond, at: 2009/10/22 06:46
Moderators: catux
Time to create page: 0.159 seconds