links for extern packages (linux,imac)

Robert Janusz wrote on Mar 10, 2011

There are unresolved links in extern packages after installation.

I have no problem with extern packages fitsutil, mscred, stsdas, tables when I create in their folders links

bin -> bin.linux
bin.linux -> bin.redhat

for the linux architecture and if "bin.linux/bin.redhat" do not coincide (analogically for imac).

---

Robert Janusz wrote on Mar 10, 2011

Here is an example that the links are not correct for linux architecture in, for example, stsdas:

implot dev$pix
:.snap psi_land

Output

Can not open... (stsdas$bin($arch)/x_psike...)

making a link

bin.linux -> bin.redhat

and commands

:.snap psi_land

and then

gflush

works OK.

in stsdas/lib there are unresolved links;
making a link

bin -> bin.linux

makes them resolved

---

Mike Fitzpatrick wrote on Mar 10, 2011

The PSIKERN binary is an exception: The CL will look in the bin.redhat binary for tasks even if the normal architecture is 'linux', however the psikern binary is defined in the dev$graphcap file with a path built on the 'arch' environment variable (here, 'linux') and so wouldn't be found when the binaries are in bin.redhat. The STSDAS sources we distribute has the bin.linux link you suggest so a 'make update' of the extern package will also fix your problem.

Otherwise, the links in the lib directory are only used when the package is being developed and are correct when the package is configured for a specific architecture. Delete them if you like.

---

Last post on Mar 10, 2011