Issues installing with conda #4053
Comments
|
@Elena-Rom Thanks for the post. Apologies, but I am not seeing the errors. I am seeing that the solver wants to use packages that supersede other packages, but this is not an error. Would you mind posting the error you are seeing? Thanks! |
|
The main error I'm getting is just a generic segmentation fault whenever I try to run any ISIS command, even though it looks like all the installation and setup is completed successfully. My only guess as to what could be causing this is the messages about the failure to solve the environment with a frozen solve that I pasted as part of the output. This is a clean install of Miniconda and a clean environment, so it's not really clear to me why there would be issues with conflicts between packages. |
|
@Elena-Rom Thanks! Can you post a screen shot or paste the error that you are seeing? That will help us out. Is the error occurring for GUI applications? Or the command line? or both? |
|
This still installs the wrong version of Can you try this and see if it fixes things: conda activate <isis_env_name>
conda install gsl=4.6 -yIf it fixes your problem, it's worth to make sure you never get an older version of it by pinning its version like so: conda activate <isis_env_name>
conda config --env --add pinned_packages "gsl>3.5" |
|
I updated my GSL to 2.6 (which looks like the most recent update) and am still having the same issue. I've gotten a few command line programs to work since posting this; however running a GUI command like qview just gives me |
|
@Elena-Rom What version of armadillo do you have? Here's the armadillo version we're seeing on our test installation: |
|
@jessemapel Mine is version 9.900.3 (I had an issue with armadillo after installing and manually updated it to fix it, which is probably why it's different). I just tried downgrading to 9.200.7 like yours and was still seeing the same issue. |
|
@Elena-Rom Can you post your current environment and I'll compare it against ours/try to reproduce this. |
|
|
I may be having a related issue - you can see it described with the link Dave posted above (libraries error #4103 ). I installed ISIS 4.2.0 and get shared libraries errors when I try to run ISIS commands. |
|
Okay, I've been looking into this and am not seeing a whole lot of things that could be causing it. The differences I see between your env and the one I have locally are very small. @Elena-Rom Can you try activating your environment and then run |
|
Bringing that difference in line didn't fix the issue. I did try running valgrind on qview to see if I could get more info on the seg fault, and it looks like there are several things going on: Maybe this will help track it down? |
|
@Elena-Rom Sorry we haven't gotten back on this issue. We're working through some troubles with the installation environment (see #4165). I would like to get back to this after we've resolved those and see if it fixes this too. Has anything changed on this? Do you have the same issue with ISIS 4.3.0? |
|
Thank you for your contribution! Unfortunately, this issue hasn't received much attention lately, so it is labeled as 'stale.' If no additional action is taken, this issue will be automatically closed in 180 days. |
github-actions
bot
added
the
inactive
ISIS version(s) affected: 4.2.0
Description
I'm trying to install ISIS through conda as recommended in the installation instructions, on a clean install of Miniconda on Ubuntu 18.04. However, when installing ISIS, I get a set of warning messages about difficulties solving the environment (attached at the bottom). The installation seems to proceed normally after that and everything is downloaded and set up successfully. However, when I try to run an ISIS command (e.g. qview), I first get that certain versions of armadillo and gsl are missing. I fix this by updating those packages, then get segmentation faults and no other info whenever I try to run any command.
I've tried uninstalling and reinstalling both Miniconda and Anaconda and trying to install ISIS 3.10.0 instead, and everything resulted in the same issue. The issue was reproduced a few days ago by somebody else trying to install in the same way on another Linux machine.
How to reproduce
Installing ISIS as recommended in the installation instructions.
Additional context
Here is the output I get during the installation process:
The text was updated successfully, but these errors were encountered: