-
Notifications
You must be signed in to change notification settings - Fork 407
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
Check compiler version and print helpful message #39
Comments
This addresses Issue #39 github.com//issues/39
This should work now at least for GCC, Intel and PGI. It will fail early with a helpful error message. |
Dear Folks, I need the an older version of kokkos if you please. Have tried to build it on a cray machine with gnu but getting the following error "g++: error: unrecognized command line option '-h'". It was ablt to build the old version. Thanks |
Looking at this now. |
This has nothing to do with the version of Kokkos. This is complaining about an argument to the compiler i.e. part of the CXX Flags. Kokkos never adds a -h. |
We just need to have the version checks also pipe error as well. Do you want me to add that, it "should be easy" (trademark). |
Hi, I'm trying to build Kokkos on a Cray machine and getting the above error. A Best On Mon, Aug 10, 2015 at 9:43 PM, Si Hammond notifications@github.com
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
Should have a patch any second. Si Hammond Scalable Computer Architectures On 8/10/15, 12:49 PM, "samaraseeri" notifications@github.com wrote:
|
Cannot clone. It fails with the following message git clone git@github.com:kokkos/kokkos.git Please make sure you have the correct access rights On Mon, Aug 10, 2015 at 10:14 PM, Si Hammond notifications@github.com
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
Si I don't understand how your patch would address the "-h" argument not recognized? That argument seems to come from the application which gets compiled not from Kokkos. |
Cannot clone latest change. Can anyone help. Best $ git clone git@github.com:kokkos/kokkos.git Please make sure you have the correct access rights On Tue, Aug 11, 2015 at 12:34 AM, Christian Trott notifications@github.com
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
@samaraseeri |
Now getting: git clone git@github.com:kokkos/kokkos.git Please make sure you have the correct access rights On Tue, Aug 11, 2015 at 1:19 AM, hcedwar notifications@github.com wrote:
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
The -h comes from the Makefile seeing GNU as Cray doesn't it? Si Hammond From: Christian Trott notifications@github.com Si I don't understand how your patch would address the "-h" argument not recognized? That argument seems to come from the application which gets compiled not from Kokkos. Reply to this email directly or view it on GitHubhttps://github.com//issues/39#issuecomment-129616301. |
When try to clone I get : git clone git@github.com:kokkos/kokkos.git Please make sure you have the correct access rights On Tue, Aug 11, 2015 at 2:00 AM, Si Hammond notifications@github.com
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
When try to clone I get : git clone git@github.com:kokkos/kokkos.git Please make sure you have the correct access rights Best On Tue, Aug 11, 2015 at 2:04 AM, Samar Aseeri samar.aseeri@kaust.edu.sa
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
Ah the -hstd=c++11 I overlooked that. Yes thats right. Samaraseeri: try cloning via the https route: |
Yes, the build completed. Thanks for the help. Best On Tue, Aug 11, 2015 at 2:04 AM, Christian Trott notifications@github.com
Samar Aseeri, PhD This message and its contents, including attachments are intended solely |
I have/(had) a test case which caught the -hstd=c++11 here so regardless it is an issue :(. |
I think this is addressed please reopen if not. |
When we got compilation errors, Christian said it was due to our having an old compiler. Unfortunately, cmake didn't tell us that. Christian said, "I think Cmake doesn’t identify the compiler version internally. Though we could at least stop inside of Kokkos earlier. (I.e. Stop right away at the first compilation step with a compile time assert and a helpful message). Can you open an issue for that on the kokkos github page?"
Thanks.
Karen
The text was updated successfully, but these errors were encountered: