-
Notifications
You must be signed in to change notification settings - Fork 86
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
2.0.0 fails to build: error: 'cl_platform_id' was not declared in this scope; did you mean 'cl_platform_info'?
etc.
#759
Comments
@kris-rowe The earlier version compiled fine on the same system, so it should be fixable. (In the worst case maybe just add a configure option to disable OpenCL when it is not supported?) |
@kris-rowe Any update on this? I would like to update the port in MacPorts, but this is a stopper. |
@barracuda156 Apologies for the delay. I am looking into this now. |
@kris-rowe Great, thank you! |
@barracuda156 If you explicitly set The error message that |
@kris-rowe I am back to the machine tomorrow and will run the build with the suggested option. It is possible that Apple framework headers are either incomplete on 10.6 ppc or arch-specific (libraries are Intel-only, there is no OpenCL on any powerpc, AFAIK). Likely the first. So OpenCL might be detected as present (if the check is for the header, not compilation with linking), while in reality it is unusable. 10.6.8 will have standard headers, but no ppc slices in OpenCL. It will probably define everything which is expected from 10.6, but linking will break down. If configure option works, that solves the problem, I can just require it for any powerpc and for < 10.6 any arch. |
@kris-rowe So it indeed detects OpenCL as being present due to the framework existing:
(Problem is that the framework does not support the arch of the build.) And disabling OpenCL does not work, unfortunately. It still fails here:
Is there a way to let the configure know that OpenCL does not exist and bypass the check completely? |
Something strange going on with the check in fact. CMake log shows it fails:
But CMake cache has:
Configure output:
|
Maybe we just need I used before |
Ok, I still think that OpenCL usage should not be based merely on its presence but also on CMake check success, but if this is an intended behavior, then the issue can be closed. |
The CMake options were renamed in By default these are all set to If you are building with GNUMake and CMake out of the same source directory, watch out for the issue described in #745 as well. |
CMake in MacPorts builds out-of-tree by default, so no issues here. And I have fixed ENABLE* options in the portfile, thank you. |
The port updated in macports/macports-ports@403d19b |
@kris-rowe Kris, could you please take a look?
Looks like the code from #730 does not work correctly in some cases:
The text was updated successfully, but these errors were encountered: