-
Notifications
You must be signed in to change notification settings - Fork 12
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
[SOLVED] Install Problem with Anaconda: "lib64/crti.o: file not recognized: file format not recognized" #18
Comments
Uh... yikes. My initial guess (and it's a guess!) is that this is to do with the C compiler. Anaconda is trying to use a combination of the system and it's own gcc in a confused manner, and therefore it can't find some internal libraries it's looking for. I can't give you a cleaner answer than that as I don't really know - it's an Anaconda gcc issue, not pyatomdb, and it's way beyond my expertise. One suggestion which might work is manually compiling the c code. Find the file linear_approx.c and change to its directory maybe that'll work? |
Thanks. I will try this and also look into anaconda gcc issue. |
I think it's something to do with 32 vs 64 bit compiled libraries, but don't quote me on that |
so this |
So far, everything works fine. I was able to reproduce the emissivity of XSPEC to high accuracy. |
Great. I am going to close this, though I know it's not exactly fixed as such. |
So, I had the same issue stated here when installing a totally different python package, where something needed to be compiled during the installation. Based on this I found a solution, which also works here. One needs to install anacondas most recent compiler before the package installation:
The inspiration came when studying this site: |
Thank you! This is great to know for the future. |
Since I stumbled over this while searching for the same error in another package: |
Thanks a lot for this comment. This also explains why installing anacondas most recent compiler solved the issue, which is probably also the safer fix in comparison to temporarily renaming conda's own |
Below is the full error message. Any ideas?
FYI, same result when using
pip
.The text was updated successfully, but these errors were encountered: