Hi Brad, Tim,
Tim wrote:
> That's really weird. Is libcfitsio.dylib in /star/lib?
> and is /star/lib/libgaia4.3.0.dylib present?
Yes, they are present.
Tim also wrote:
> and when it's set what value does it have?
I think DYLD_LIBRARY_PATH was not set at all initially, which is why
it returned blank when I asked:
printenv DYLD_LIBRARY_PATH
Brad wrote:
>
> Essentially what you're going to have to do is to ensure that
> DYLD_LIBRARY_PATH is set to /star/lib if you're going to use any Starlink
> applications, and that it's unset if you're using the other stuff that
> crashes when it's set.
>
This does help. I have now included these lines in my bash .profile:
# initialize starlink commands for bash shell
source /star/etc/profile
alias setstarpath="export DYLD_LIBRARY_PATH=/star/lib"
alias unsetstarpath="unset DYLD_LIBRARY_PATH"
# -- note: most starlink apps will not work without DYLD_LIBRARY_PATH --
# -- note: setstarpath breaks things outside starlink --
This allows me to switch back and forth between starlink working and
everything else working. I can also have one terminal with the
starlink library path set, and another terminal where it is not set so
that I can run other apps from there.
Mahalo!
--
Matthijs
--
M.H.D. van der Wiel
Kapteyn Astronomical Institute, University of Groningen
& SRON Netherlands Institute for Space Research
e-mail: [log in to unmask]
homepage: http://www.astro.rug.nl/~wiel/
room: ZG 183 [Landleven 12]
tel: +31 (0)50 363 4083
|