-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with ds9 7.6 on Mac OSX and non-RHEL-6 Linux #410
Comments
Which version of OSX are you running? |
Software: (edited to remove possibly sensitive information)
I don't have anything installed under /opt/local |
Thank you. There are problems with the new
|
@rendinam I see this is still open...ds9 now has a 8.0.1 release which we should build and serve here, perhaps the shared library issue isn't an issue anymore? It's fine on my mac. |
^ Yeah, I think we fixed the shared library issue by linking against the |
The OSX packages are functional once again, but I am still seeing |
I just downloaded the current version of astroconda onto a freshly-installed Ubuntu 18.04 system, and I still have this problem..."libssl.so.10:cannot open...". I was able to circumvent the problem by replacing astroconda's version of ds9 with a working copy of ds9 7.5 |
@fsc137 Thank you! |
Get a run-time copy of ds9 for your operating system from the ds9 website.
The astroconda copy of ds9 will be buried in a subdirectory under the
directory where anaconda was installed.
You can find it by
cd /* takes you to your home
directory */
find . -name "ds9" -print /* lists your various copies of ds9 */
So... just remove the ds9 executable that resides in the bin under anaconda
and astroconda and replace it with the version that works.
This may be undone by anaconda the next time you update and you'll have to
re-do it, but doing this won't harm anything.
The point is, that anaconda manipulates your $PATH to use its version of
ds9 rather than any other. Putting the
working version of ds9 in the "bin" prioritized by that $PATH will cause it
to use the correct executable.
Only the astroconda folks at STSI can really fix this permanently.
…On Mon, Sep 9, 2019 at 10:47 AM Katie Frey ***@***.***> wrote:
@fsc137 <https://github.com/fsc137>
Could you give me a quick walk through of how to replace astroconda's
version of ds9 with a working copy of ds9 7.5?
Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#410?email_source=notifications&email_token=AAGAN7AVSOGZTCSGA7J4KXTQIZOWRA5CNFSM4FZDFBX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6H3IKA#issuecomment-529511464>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGAN7DP4RFWE4UVSSLJQ6DQIZOWRANCNFSM4FZDFBXQ>
.
|
Thank you so much, that worked perfectly! |
@katieefrey If you are working with astroconda, you can install any version of ds9 and pin it from future update as follows:
If you want to downgrade and pin ds9 in some environment, say iraf27, then |
When installing the latest ds9 build on Mac OSX, the following error is encountered when trying to start ds9:
The text was updated successfully, but these errors were encountered: