-
Notifications
You must be signed in to change notification settings - Fork 8
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
cl-mpi and debian 8 #2
Comments
Greetings! The short answer: The long answer: I hope this solves the problem. My development platform is also Debian 8, so I am optimistic. If not I would like to see the output of Best regards, |
Thanks. I get this:
When I run that from the command line, I get this:
And the mpicc output:
|
Thank you for the helpful output! The output on the command line should begin with
It appears another |
Got the new commit, seeing the same issue. Here's more output:
|
If this does not fix it, i have just discovered that CFFI determines the C compiler with
so unsetting the environment variable $CC or setting it to mpicc might help. |
Progress! Unsetting CC worked for cl-mpi. Unfortunately, I think unsetting it breaks some other projects. I'll run through building the universe and see what happens with no CC. |
If it helps I can detect if $CC is set and if so, bind it to mpicc for the dynamic extent of the CFFI grovelling and restore it afterwards. Then other projects can use $CC as they want. I only fear changing environment variables (even for such a short duration) could be a horrible source of nondeterminism for automated build systems. What do you think? |
I unset CC in my build process. cl-mpi started working, and nothing broke. I'm going to leave it unset and consider things fixed. Thanks for your help! |
I'm trying to build on debian 8. It installs mpi.h in /usr/lib/openmpi/openmpi/include/mpi.h. What should I do to help cl-openmpi find it?
The text was updated successfully, but these errors were encountered: