-
Notifications
You must be signed in to change notification settings - Fork 26
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
dyld: Symbol not found: _util_malloc_ #16
Comments
@DanielLenz I think this is a Mac specific issue. For some reason it is not finding one of the libraries. Does it work if you do Please, let us know of the outcome so we can add instructions to the |
I'm afraid not. |
Thanks! I'll look deeper into it. |
@DanielLenz What compiler (and version) did you use to compile this? And was it the same that you used to install libsharp and any other libraries? |
Also, could you check if the problem gets fixed if you do:
? |
Thank for helping me to debug this!
NaMaster [master●] which gcc
gcc: aliased to /usr/local/bin/gcc-7
NaMaster [master●] gcc --version
gcc-7 (Homebrew GCC 7.2.0) 7.2.0
Good point, I might have used clang or gcc-6 to do that. I can fetch the latest libshard and fftw3 and fix that.
I'm afraid that didn't work. |
@DanielLenz I did a little bit of digging and it turns out that the |
@damonge has just prepared a fix with which you don't even need to export these flags. Please, check it out at the |
Please let us know if it works, and we'll merge it |
Awesome, thanks for fixing this so rapidly! One little issue popped up, everything else passed:
Now looking into the python wrapper... |
Installing python didn't raise any issues, all the unittests I ran with |
Yeah, @fjaviersanchez mentioned that one. It's weird, because travis doesn't pick it up, and all tests have passed for me in the past. I think it may be a compiler-specific floating point thing related to the issue that caused the first problem to begin with. It's even wierder because python is supposed to be running the same test. I'll have a quick look, but I wouldn't worry. Many kudos to @fjaviersanchez for figuring this one out! |
Tagging @anicola and @NicolettaK , since they had this problem too |
Thank you very much @fjaviersanchez and @damonge! Now everything works for me as well. As Daniel, I also run into a one little issue:
Apart from that, everything works like a charm! Thanks again! |
Great paper presentation today, looking forward to diving into it and using the code! Will have to debug this first, though.
Just copying the issues from damonge/NaMaster#24, where several people have run into the following:
First executing the following, which works fine.
Then running
make check
gives the following:I get the very same error when trying to run the namaster executable.
It might make sense to add a travis build that uses a typical MacOS build, to catch this and similar errors.
The text was updated successfully, but these errors were encountered: