-
Notifications
You must be signed in to change notification settings - Fork 578
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
Xpetra: cmake logic to solve GlobalOrdinal conflict #6019
Conversation
When Tpetra deprecated code is removed, its default GO will be long long. Epetra is enabled by default but with 32-bit GO. Previously if Epetra32 was enabled and Tpetra GO=int was off, Xpetra would error out at configure time. This means that without deprecated code, a Trilinos build with MueLu/Xpetra enabled and every option default would fail to configure. This change catches the situation above. If Epetra is explicitly enabled by the user, it errors out like before. But if Epetra is only implicitly enabled and GO=long long, Xpetra will just warn and disable its Epetra support.
Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request. |
Status Flag 'Pull Request AutoTester' - Testing Jenkins Projects: Pull Request Auto Testing STARTING (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
Using Repos:
Pull Request Author: brian-kelley |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Status Flag 'Pull Request AutoTester' - Jenkins Testing: all Jobs PASSED Pull Request Auto Testing has PASSED (click to expand)Build InformationTest Name: Trilinos_pullrequest_gcc_4.8.4
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_intel_17.0.1
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_4.9.3_SERIAL
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_gcc_7.2.0
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_cuda_9.2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_2
Jenkins Parameters
Build InformationTest Name: Trilinos_pullrequest_python_3
Jenkins Parameters
|
Status Flag 'Pre-Merge Inspection' - SUCCESS: The last commit to this Pull Request has been INSPECTED AND APPROVED by [ jhux2 ]! |
Status Flag 'Pull Request AutoTester' - AutoMerge IS ENABLED, but the Label AT: AUTOMERGE is not set. Either set Label AT: AUTOMERGE or manually merge the PR... |
When Tpetra deprecated code is removed, its default GO will be long
long. Epetra is enabled by default but with 32-bit GO. Previously if
Epetra32 was enabled and Tpetra GO=int was off, Xpetra would error out
at configure time.
This means that without deprecated code, a Trilinos build with
MueLu/Xpetra enabled and every option default would fail to configure.
This change catches the situation above. If Epetra is explicitly
enabled by the user, it errors out like before. But if Epetra is
only implicitly enabled and GO=long long, Xpetra will just warn
and disable its Epetra support, so configuration will succeed
and Xpetra+downstream will just use Tpetra and GO=long long.
@trilinos/xpetra
Description
Motivation and Context
This will fix configure when deprecated code is disabled or removed, as shown in this
nightly on rocketman: https://testing-dev.sandia.gov/cdash/viewConfigure.php?buildid=4900214
How Has This Been Tested?
Checklist