Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Get Trilinos building with CMake + Ninja + Fortran #269

Closed
bartlettroscoe opened this issue Apr 5, 2016 · 4 comments
Closed

Get Trilinos building with CMake + Ninja + Fortran #269

bartlettroscoe opened this issue Apr 5, 2016 · 4 comments
Labels
Framework tasks Framework tasks (used internally by Framework team) resolved: duplicate Issue is really a duplicate of some other issue where the efforts will be focused story The issue corresponds to a Kanban Story (vs. Epic or Task)

Comments

@bartlettroscoe
Copy link
Member

This story is to get all of Trilinos building with CMake + Ninja with Fortran turned on. There is a branch of Ninja and CMake that supports projects with Fortran code. This story will track efforts to get Trilinos and CMake + Ninja + Fortran working.

CC: @nmhamster. @bathmatt
@bartlettroscoe bartlettroscoe added Framework tasks Framework tasks (used internally by Framework team) story The issue corresponds to a Kanban Story (vs. Epic or Task) stage: in progress Work on the issue has started labels Apr 5, 2016
@bartlettroscoe
Copy link
Member Author

This story is already in progress. Currently there is a problem with Ninja rebuilding every Fortran file after every minor reconfigure. Details will be forthcoming.

@bradking
Copy link
Contributor

bradking commented Apr 5, 2016

So far we've found that ninja -d explain shows many lines like:

ninja explain: output packages/epetra/src/CMakeFiles/epetra.dir/Epetra_dcrsmm.f-pp.f older than most recent input /home/mbetten/Trilinos/builds/build_for_panzer/gcc/debug (1459543581 vs 1459543674)

This looks like a dependency on a directory instead of a file. We need to figure out why that dependency appears.

EDIT: This investigation has moved to #261. See discussion there for updates.

@bartlettroscoe
Copy link
Member Author

I think this is a CUDA build. Is that right @bathmatt?

@bartlettroscoe
Copy link
Member Author

I have replacing this story with the larger epic/milestone "Get Trilinos building with CMake + Ninja + Fortran".

@bartlettroscoe bartlettroscoe added resolved: duplicate Issue is really a duplicate of some other issue where the efforts will be focused stage: in progress Work on the issue has started and removed stage: in progress Work on the issue has started labels Apr 6, 2016
bartlettroscoe added a commit that referenced this issue Oct 11, 2018
@bartlettroscoe
Automatic snapshot commit from tribits at 373c6d2
38683d1 
Origin repo remote tracking branch: 'github/master'
Origin repo remote repo URL: 'github = [email protected]:TriBITSPub/TriBITS.git'

At commit:

commit 373c6d241b2de5373ef0525fa99aa0151eae35a5
Author:  Roscoe A. Bartlett <[email protected]>
Date:    Thu Oct 11 15:48:20 2018 -0600
Summary: TRIBITS_CTEST_DRIVER(): Correctly pass in excluded package disables for all-at-once approach (#269)
tjfulle pushed a commit to tjfulle/Trilinos that referenced this issue Dec 6, 2018
@bartlettroscoe @tjfulle
Automatic snapshot commit from tribits at 373c6d2
8d0f460 
Origin repo remote tracking branch: 'github/master'
Origin repo remote repo URL: 'github = [email protected]:TriBITSPub/TriBITS.git'

At commit:

commit 373c6d241b2de5373ef0525fa99aa0151eae35a5
Author:  Roscoe A. Bartlett <[email protected]>
Date:    Thu Oct 11 15:48:20 2018 -0600
Summary: TRIBITS_CTEST_DRIVER(): Correctly pass in excluded package disables for all-at-once approach (trilinos#269)
@trilinos-autotester trilinos-autotester mentioned this issue Jul 15, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework tasks Framework tasks (used internally by Framework team) resolved: duplicate Issue is really a duplicate of some other issue where the efforts will be focused story The issue corresponds to a Kanban Story (vs. Epic or Task)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bradking @bartlettroscoe