COLOR Installation Problem (fwd)
Mike Fitzpatrick wrote on Jun 13, 2006
[MOD NOTE: Forwarded from comment]
Authored by: Anonymous on Tuesday, June 13 2006 @ 03:37 PM MDT
When I try to install locally the color package, there is a "color" added everywhere :
mkpkg -p color linux will result in
envinit: cannot open `/data/color/colorlib/zzsetenv.def' - lib is OK, not colorlib
Same thing if I use the redhat binary :
ERROR: Cannot open connected subprocess (colorsrc$x_color.e) - src is OK, not colorsrc
although the definition in the login.cl is
reset color = /data/color/
task $color.pkg = color$color.cl
anyone can help ?
yael naze
naze@astro.ulg.ac.be
Authored by: Anonymous on Tuesday, June 13 2006 @ 03:37 PM MDT
When I try to install locally the color package, there is a "color" added everywhere :
mkpkg -p color linux will result in
envinit: cannot open `/data/color/colorlib/zzsetenv.def' - lib is OK, not colorlib
Same thing if I use the redhat binary :
ERROR: Cannot open connected subprocess (colorsrc$x_color.e) - src is OK, not colorsrc
although the definition in the login.cl is
reset color = /data/color/
task $color.pkg = color$color.cl
anyone can help ?
yael naze
naze@astro.ulg.ac.be
Mike Fitzpatrick wrote on Jun 13, 2006
Package environments are only picked up from either the hlib$extern.pkg file or the unix environment. Defining the package in your login.cl is sufficient to run it (so long as it is before the final 'keep' statement), however to build it you should do something like
Be sure the package is first configured for your architecture before building and note that the EXPORT task may already do what you want.
-Mike
unix% setenv color /data/color/ # trailing '/' required
unix% mkpkg -p color # assuming you're in the color dir
Be sure the package is first configured for your architecture before building and note that the EXPORT task may already do what you want.
-Mike
Last post on Jun 13, 2006