Trilinos issueshttps://gitlab.osti.gov/jmwille/Trilinos/-/issues2016-06-30T15:13:17Zhttps://gitlab.osti.gov/jmwille/Trilinos/-/issues/473Migrate checklists to GitHub Trilinos Developer site2016-06-30T15:13:17ZJames WillenbringMigrate checklists to GitHub Trilinos Developer site*Created by: jwillenbring*
**Next Action Status:**
Updating the new developer checklist ...
**CC:** @trilinos/framework
**Description:**
The process checklists need to be moved from the old developer website to the new Trilinos Dev...*Created by: jwillenbring*
**Next Action Status:**
Updating the new developer checklist ...
**CC:** @trilinos/framework
**Description:**
The process checklists need to be moved from the old developer website to the new Trilinos Developer GitHub wiki.
**Tasks:**
1. Update the new-developer checklist ... IN PROGRESS..
2. ???
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/471Cdash is not showing results2016-06-29T14:14:48ZJames WillenbringCdash is not showing results*Created by: bmpersc*
Cdash doesn't seem to be showing its results. However, the checking I've done indicates that the submissions have been received and are not backed up. It is unclear why they are not showing on the dashboard. I will...*Created by: bmpersc*
Cdash doesn't seem to be showing its results. However, the checking I've done indicates that the submissions have been received and are not backed up. It is unclear why they are not showing on the dashboard. I will need to dig into this more
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/468Fails to use then supplied openmpi path2016-06-27T20:01:43ZJames WillenbringFails to use then supplied openmpi path*Created by: yurivict*
On FreeBSD OpenMPI headers are in /usr/local/mpi/openmpi/include. During configure and build stages CXXFLAGS has -L flag with this folder.
cmake has these arguments:
```
-DTrilinos_ENABLE_OpenMP:BOOL=ON
-DTPL_EN...*Created by: yurivict*
On FreeBSD OpenMPI headers are in /usr/local/mpi/openmpi/include. During configure and build stages CXXFLAGS has -L flag with this folder.
cmake has these arguments:
```
-DTrilinos_ENABLE_OpenMP:BOOL=ON
-DTPL_ENABLE_MPI:BOOL=ON
-DMPI_BASE_DIR:PATH="/usr/local/mpi/openmpi"
-DMPI_BIN_DIR:PATH="/usr/local/mpi/openmpi/bin"
```
Yet build still breaks with this error:
```
/usr/ports/math/trilinos/work/Trilinos-trilinos-release-12-6-2/packages/zoltan/src/include/zoltan.h:50:17: fatal error: mpi.h: No such file or directory
#include <mpi.h>
```
System calls trace shows that the "openmpi" folder is never looked at for mpi.h.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/26Trilinos/README.md way out of date2016-06-20T12:58:14ZJames WillenbringTrilinos/README.md way out of date*Created by: bartlettroscoe*
The file Trilinos/README.md that is displayed as the first thing people see on GitHub is way out of date (and has been for many months or more). Most of the links are broken and the file names are way out o...*Created by: bartlettroscoe*
The file Trilinos/README.md that is displayed as the first thing people see on GitHub is way out of date (and has been for many months or more). Most of the links are broken and the file names are way out of date. This does not make for a good first impression for new people coming to look at Trilinos on GitHub. At the very least, this should be gutted and just point to trilinos.org. Then, if someone has time, this can be filled out.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/255Prepare cmake arguments for parameterized Jenkins nightly builds2016-05-26T04:09:16ZJames WillenbringPrepare cmake arguments for parameterized Jenkins nightly builds*Created by: jwillenbring*
@bmpersc
As part of getting proper nightly testing back in place, and making jobs float on the Jenkins build farm, we are going to start by getting build arguments for working Trilinos configurations. These ...*Created by: jwillenbring*
@bmpersc
As part of getting proper nightly testing back in place, and making jobs float on the Jenkins build farm, we are going to start by getting build arguments for working Trilinos configurations. These configurations include GCC MPI/SERIAL, Intel MPI/SERIAL, and CLANG MPI/SERIAL. The MPI jobs will share one common set of arguments, as will the SERIAL jobs. The variation will come from loading the applicable set of modules from the SEMS NFS mount, and related environment variables.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/363Set up my.cdash.org for Trilinos2016-05-26T04:02:25ZJames WillenbringSet up my.cdash.org for Trilinos*Created by: jwillenbring*
Setting up a (possibly temporary) CDash dashboard on my.cdash.org was discussed at the Spring Developer Meeting last week. Erik S. has granted approval for this. This should help get our nightly testing result...*Created by: jwillenbring*
Setting up a (possibly temporary) CDash dashboard on my.cdash.org was discussed at the Spring Developer Meeting last week. Erik S. has granted approval for this. This should help get our nightly testing results posting properly again.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/374Create a list of supported compilers/ TPLs2016-05-20T21:47:02ZJames WillenbringCreate a list of supported compilers/ TPLs*Created by: jwillenbring*
@trilinos/framework @jhux2 @crtrott
At the 2016 Trilinos Spring Developer meeting it was mentioned that a list of supported compilers/TPLs would be useful. This has been mentioned before. Maintaining this li...*Created by: jwillenbring*
@trilinos/framework @jhux2 @crtrott
At the 2016 Trilinos Spring Developer meeting it was mentioned that a list of supported compilers/TPLs would be useful. This has been mentioned before. Maintaining this list would be difficult. At the meeting, it was suggested that perhaps the current CDash builds would represent the supported versions. However, digging in and finding all TPL versions would be difficult.
Another suggestion was to maintain a shorter list of versions at least known to work. This would also take effort to maintain, but potentially wouldn't be as bad.
I would like to have a little more discussion in this ticket before deciding on a specific path-forward. Feel free to mention other interested people.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/45Download with mandatory sign-up2016-05-19T23:32:19ZJames WillenbringDownload with mandatory sign-up*Created by: nschloe*
There are many straightforward ways to get Trilinos nowadays:
- `git clone` from GitHub
- [download a release from GitHub](https://github.com/trilinos/Trilinos/releases)
- get it from [Debian](https://tracker.debia...*Created by: nschloe*
There are many straightforward ways to get Trilinos nowadays:
- `git clone` from GitHub
- [download a release from GitHub](https://github.com/trilinos/Trilinos/releases)
- get it from [Debian](https://tracker.debian.org/pkg/trilinos)
- get it from the [nightly PPA](https://launchpad.net/~nschloe/+archive/ubuntu/trilinos-nightly/)
Oh, and of course the [official download page](https://trilinos.org/download/) which [requires you to sign up before download](https://trilinos.org/oldsite/download/login.html?tid=tr12042bz2). Rather than helping the distribution of Trilinos, the sign-up hinders it. The gain that one supposedly gets from that is a user statistics, but in the light of the alternative download methods listed above, this statistic is practically worthless.
I suggest to remove the sign-up requirement from the download page.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/373Set up CDash service with my.cdash.org2016-05-19T16:56:41ZJames WillenbringSet up CDash service with my.cdash.org*Created by: jwillenbring*
I have worked out the details of how to pay for this. I have received approval to do it from Erik S.
I need to figure out who "owns" the trilinos account already on my.cdash.org. We would like to use the offi...*Created by: jwillenbring*
I have worked out the details of how to pay for this. I have received approval to do it from Erik S.
I need to figure out who "owns" the trilinos account already on my.cdash.org. We would like to use the official name.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/127Compile Issues with Boost Includes on IBM POWER8 with XL 13.1.3 Compiler2016-05-11T13:43:25ZJames WillenbringCompile Issues with Boost Includes on IBM POWER8 with XL 13.1.3 Compiler*Created by: nmhamster*
Build errors seen in Trilinos VOTD when compiling using IBM XL 13.1.3 compiler. Recording for logging purposes, discussion on-going with IBM team for approach to fix this.
```
/home/projects/power8/boost/1.59.0/...*Created by: nmhamster*
Build errors seen in Trilinos VOTD when compiling using IBM XL 13.1.3 compiler. Recording for logging purposes, discussion on-going with IBM team for approach to fix this.
```
/home/projects/power8/boost/1.59.0/openmpi/1.10.1/ibm/13.1.3/cuda/7.5.7/include/boost/type_traits/type_with_alignment.hpp:111:11: error:
pasting formed 'BOOST_PP_LIST_IS_CONS_(', an invalid preprocessing token
/home/projects/power8/boost/1.59.0/openmpi/1.10.1/ibm/13.1.3/cuda/7.5.7/include/boost/type_traits/type_with_alignment.hpp:64:30: note: expanded from macro 'BOOST_TT_ALIGNMENT_TYPES'
BOOST_TT_ALIGNMENT_STRUCT_TYPES)
^
/home/projects/power8/boost/1.59.0/openmpi/1.10.1/ibm/13.1.3/cuda/7.5.7/include/boost/type_traits/type_with_alignment.hpp:58:9: note:
expanded from macro 'BOOST_TT_ALIGNMENT_STRUCT_TYPES'
BOOST_PP_LIST_TRANSFORM(BOOST_TT_HAS_ONE_T, \
^
/home/projects/power8/boost/1.59.0/openmpi/1.10.1/ibm/13.1.3/cuda/7.5.7/include/boost/preprocessor/list/transform.hpp:25:79: note:
expanded from macro 'BOOST_PP_LIST_TRANSFORM'
# define BOOST_PP_LIST_TRANSFORM(op, data, list) BOOST_PP_TUPLE_ELEM(3,
2, BOOST_PP_LIST_FOLD_RIGHT(BOOST_...
```
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/78Create 12.6 branch2016-04-06T21:01:49ZJames WillenbringCreate 12.6 branch*Created by: bmpersc*
*Created by: bmpersc*
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/269Get Trilinos building with CMake + Ninja + Fortran2016-04-06T20:29:28ZJames WillenbringGet Trilinos building with CMake + Ninja + Fortran*Created by: bartlettroscoe*
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 ...*Created by: bartlettroscoe*
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
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/268Revise "Getting Started" section of Trilinos.org website2016-04-05T03:36:36ZJames WillenbringRevise "Getting Started" section of Trilinos.org website*Created by: maherou*
The "Getting Started" section of Trilinos documentation needs revision.
It also needs better visibility from the main trilinos.org page and from the GitHub site.
Specific changes:
- Provide a short write up about h...*Created by: maherou*
The "Getting Started" section of Trilinos documentation needs revision.
It also needs better visibility from the main trilinos.org page and from the GitHub site.
Specific changes:
- Provide a short write up about how to manage debug vs. release builds when using TriBITS.
- Update the Cmake reference content.
Put it on our Trilinos GitHub Quickstart webpage.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/251Remove MeshingGenie2016-03-30T16:40:33ZJames WillenbringRemove MeshingGenie*Created by: nschloe*
As highlighted in bug #247, MeshingGenie is obsolete and should be removed from Trilinos.
*Created by: nschloe*
As highlighted in bug #247, MeshingGenie is obsolete and should be removed from Trilinos.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/24duplicate TPL adapters2016-03-23T06:14:42ZJames Willenbringduplicate TPL adapters*Created by: nschloe*
In Trilinos, TriBits takes care of some of the TPL integration via the files in
```
cmake/tribits/common_tpls/FindTPL*.cmake
```
Their counterparts in
```
cmake/TPLs/FindTPL*.cmake
```
are redundant and should ...*Created by: nschloe*
In Trilinos, TriBits takes care of some of the TPL integration via the files in
```
cmake/tribits/common_tpls/FindTPL*.cmake
```
Their counterparts in
```
cmake/TPLs/FindTPL*.cmake
```
are redundant and should probably be removed.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/149boostlib defines not being respected.2016-03-16T15:08:31ZJames Willenbringboostlib defines not being respected.*Created by: bathmatt*
On hansen I'm working on building trilinos and I have set every thing I can think of to set the boost library paths.
dir-debug (gcc) 20 $ grep BoostL configure-drekar.sh
-D TPL_ENABLE_BoostLib=ON \
-D TPL_BoostLi...*Created by: bathmatt*
On hansen I'm working on building trilinos and I have set every thing I can think of to set the boost library paths.
dir-debug (gcc) 20 $ grep BoostL configure-drekar.sh
-D TPL_ENABLE_BoostLib=ON \
-D TPL_BoostLib_INCLUDE_DIRS:FILEPATH="${BOOST_BASE_DIR}/include" \
-D TPL_BoostLib_LIBRARY_DIRS:FILEPATH="${BOOST_BASE_DIR}/lib" \
-D TPL_BoostLib_LIBRARIES="${BOOST_BASE_DIR}/lib/libboost_program_options.so;${BOOST_BASE_DIR}/lib/libboost_system.so" \
However, cmake ignores this and just uses -lboost_system as shown below. This happens on lots of different systems, hansen, chama are just two I can think of. I have a long email thread with Ross but that hit a dead end.
[config.out.txt](https://github.com/trilinos/Trilinos/files/138446/config.out.txt)
/home/projects/x86-64-haswell/openmpi/1.10.0/gnu/4.9.3/bin/mpicxx -std=c++11 -fopenmp -g -O0 CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestAlgorithmRunner.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestCudaMgr.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestMain.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTest_helpers.cpp.o -o STKClassic_stk_algsup_unit_tests.exe -rdynamic ../stk_algsup/libstkclassic_algsup.a ../../stk_mesh/stk_mesh/fixtures/libstkclassic_mesh_fixtures.a ../../stk_mesh/stk_mesh/fem/libstkclassic_mesh_fem.a ../../stk_mesh/stk_mesh/base/libstkclassic_mesh_base.a ../../stk_util/stk_util/unit_test_support/libstkclassic_util_unit_test_support.a ../../stk_util/stk_util/parallel/libstkclassic_util_parallel.a ../../stk_util/stk_util/diag/libstkclassic_util_diag.a ../../stk_util/stk_util/environment/libstkclassic_util_env.a ../../stk_util/stk_util/util/libstkclassic_util_util.a ../../../../seacas/libraries/exodus/cbind/libexodus.a -lboost_program_options -lboost_system ../../../../fei/support-Trilinos/libfei_trilinos.a ../../../../fei/base/libfei_base.a ../../../../belos/tpetra/src/libbelostpetra.a ../../../../belos/epetra/src/libbelosepetra.a ../../../../belos/src/libbelos.a ../../../../ml/src/libml.a ../../../../galeri/src-epetra/libgaleri-epetra.a ../../../../tpetra/core/ext/libtpetraext.a ../../../../tpetra/core/inout/libtpetrainout.a ../../../../tpetra/core/src/libtpetra.a ../../../../tpetra/kernels/src/libtpetrakernels.a ../../../../kokkos/algorithms/src/libkokkosalgorithms.a ../../../../kokkos/containers/src/libkokkoscontainers.a ../../../../tpetra/classic/LinAlg/libtpetraclassiclinalg.a ../../../../tpetra/classic/NodeAPI/libtpetraclassicnodeapi.a ../../../../tpetra/classic/src/libtpetraclassic.a ../../../../ifpack/src/libifpack.a ../../../../amesos/src/libamesos.a ../../../../epetraext/src/libepetraext.a ../../../../seacas/libraries/ioss/src/init/libIonit.a ../../../../seacas/libraries/ioss/src/transform/libIotr.a ../../../../seacas/libraries/ioss/src/heartbeat/libIohb.a ../../../../seacas/libraries/ioss/src/generated/libIogn.a ../../../../seacas/libraries/ioss/src/pamgen/libIopg.a ../../../../seacas/libraries/ioss/src/exo_fac/libIoexo_fac.a ../../../../seacas/libraries/ioss/src/exo_par/libIopx.a ../../../../seacas/libraries/ioss/src/exo_fpp/libIofx.a ../../../../seacas/libraries/ioss/src/exodus/libIoex.a ../../../../seacas/libraries/ioss/src/libIoss.a ../../../../seacas/libraries/exodus/cbind/libexodus.a -Wl,-Bstatic -lnetcdf -Wl,-Bdynamic -L/home/projects/x86-64-haswell-nvidia/netcdf-exo/4.3.3.1/openmpi/1.10.0/gcc/4.8.4/cuda/7.5.7/lib -lnetcdf -L/home/projects/x86-64-haswell-nvidia/hdf5/1.8.15/openmpi/1.10.0/gcc/4.8.4/cuda/7.5.7/lib -lhdf5_hl -lhdf5 -lz -ldl ../../../../pamgen/src/libpamgen_extras.a ../../../../pamgen/src/libpamgen.a ../../../../aztecoo/src/libaztecoo.a ../../../../triutils/src/libtriutils.a ../../../../epetra/src/libepetra.a ../../../../shards/src/libshards.a ../../../../zoltan/src/libzoltan.a -lm ../../../../sacado/src/libsacado.a ../../../../teuchos/kokkoscomm/src/libteuchoskokkoscomm.a ../../../../teuchos/kokkoscompat/src/libteuchoskokkoscompat.a ../../../../teuchos/remainder/src/libteuchosremainder.a ../../../../teuchos/numerics/src/libteuchosnumerics.a -L/home/projects/x86-64-haswell/lapack/3.5.0/gcc/4.8.4 -llapack -L/home/projects/x86-64-haswell/blas/20150602/gcc/4.8.4 -lblas ../../../../teuchos/comm/src/libteuchoscomm.a ../../../../teuchos/parameterlist/src/libteuchosparameterlist.a ../../../../teuchos/core/src/libteuchoscore.a -lboost_program_options -lboost_system ../../../../kokkos/core/src/libkokkoscore.a -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lgfortran -lquadmath
I even went so far as to edit the cmake dependencies file
-bash-4.1$ git diff
diff --git a/packages/stk/stk_classic/cmake/Dependencies.cmake b/packages/stk/stk_classic/cmake/Dependencies.cmake
index 0c16502..b7cd94d 100644
--- a/packages/stk/stk_classic/cmake/Dependencies.cmake
+++ b/packages/stk/stk_classic/cmake/Dependencies.cmake
@@ -4,5 +4,5 @@ SET(TEST_REQUIRED_DEP_PACKAGES SEACASExodus)
SET(TEST_OPTIONAL_DEP_PACKAGES)
SET(LIB_REQUIRED_DEP_TPLS Boost BoostLib)
SET(LIB_OPTIONAL_DEP_TPLS OpenNURBS)
-SET(TEST_REQUIRED_DEP_TPLS)
+SET(TEST_REQUIRED_DEP_TPLS BoostLib)
SET(TEST_OPTIONAL_DEP_TPLS gtest)
-bash-4.1$
dir-debug (gcc) 23 $ cmake --version
cmake version 3.3.2
CMake suite maintained and supported by Kitware (kitware.com/cmake).
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/113TriBITS picking up the wrong boost libraries.2016-02-25T15:41:18ZJames WillenbringTriBITS picking up the wrong boost libraries.*Created by: bathmatt*
Building STK_classic is finding the wrong boost. I set to a specific version of boost and try to compile and I'm getting missing symbols. The include is being propagated but the libs are not even thoush I am set...*Created by: bathmatt*
Building STK_classic is finding the wrong boost. I set to a specific version of boost and try to compile and I'm getting missing symbols. The include is being propagated but the libs are not even thoush I am setting both
-D TPL_Boost_LIBRARY_DIRS:FILEPATH="${BOOST_BASE_DIR}/lib" \
and
-D TPL_Boost_LIBRARIES="${BOOST_BASE_DIR}/lib/libboost_program_options.so;${BOOST_BASE_DIR}/lib/libboost_system.so" does not
I still get the system libs.
/home/projects/x86-64-haswell-nvidia/openmpi/1.10.0/gcc/4.8.4/cuda/7.5.7/bin/mpicxx -std=c++11 -g -O0 CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestAlgorithmRunner.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestCudaMgr.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTestMain.cpp.o CMakeFiles/STKClassic_stk_algsup_unit_tests.dir/UnitTest_helpers.cpp.o -o STKClassic_stk_algsup_unit_tests.exe -rdynamic ../stk_algsup/libstkclassic_algsup.a ../../stk_mesh/stk_mesh/fixtures/libstkclassic_mesh_fixtures.a ../../stk_mesh/stk_mesh/fem/libstkclassic_mesh_fem.a ../../stk_mesh/stk_mesh/base/libstkclassic_mesh_base.a ../../stk_util/stk_util/unit_test_support/libstkclassic_util_unit_test_support.a ../../stk_util/stk_util/parallel/libstkclassic_util_parallel.a ../../stk_util/stk_util/diag/libstkclassic_util_diag.a ../../stk_util/stk_util/environment/libstkclassic_util_env.a ../../stk_util/stk_util/util/libstkclassic_util_util.a ../../../../seacas/libraries/exodus/cbind/libexodus.a ../../../../fei/support-Trilinos/libfei_trilinos.a ../../../../fei/base/libfei_base.a ../../../../belos/tpetra/src/libbelostpetra.a ../../../../belos/epetra/src/libbelosepetra.a ../../../../belos/src/libbelos.a ../../../../ml/src/libml.a ../../../../galeri/src-epetra/libgaleri-epetra.a ../../../../tpetra/core/ext/libtpetraext.a ../../../../tpetra/core/inout/libtpetrainout.a ../../../../tpetra/core/src/libtpetra.a ../../../../tpetra/kernels/src/libtpetrakernels.a ../../../../kokkos/algorithms/src/libkokkosalgorithms.a ../../../../kokkos/containers/src/libkokkoscontainers.a ../../../../tpetra/classic/LinAlg/libtpetraclassiclinalg.a ../../../../tpetra/classic/NodeAPI/libtpetraclassicnodeapi.a ../../../../tpetra/classic/src/libtpetraclassic.a ../../../../ifpack/src/libifpack.a ../../../../amesos/src/libamesos.a ../../../../epetraext/src/libepetraext.a ../../../../seacas/libraries/ioss/src/init/libIonit.a ../../../../seacas/libraries/ioss/src/transform/libIotr.a ../../../../seacas/libraries/ioss/src/heartbeat/libIohb.a ../../../../seacas/libraries/ioss/src/generated/libIogn.a ../../../../seacas/libraries/ioss/src/pamgen/libIopg.a ../../../../seacas/libraries/ioss/src/exo_fac/libIoexo_fac.a ../../../../seacas/libraries/ioss/src/exo_par/libIopx.a ../../../../seacas/libraries/ioss/src/exo_fpp/libIofx.a ../../../../seacas/libraries/ioss/src/exodus/libIoex.a ../../../../seacas/libraries/ioss/src/libIoss.a ../../../../seacas/libraries/exodus/cbind/libexodus.a -Wl,-Bstatic -lnetcdf -Wl,-Bdynamic -L/home/projects/x86-64-haswell-nvidia/netcdf-exo/4.3.3.1/openmpi/1.10.0/gcc/4.8.4/cuda/7.5.7/lib -lnetcdf -L/home/projects/x86-64-haswell-nvidia/hdf5/1.8.15/openmpi/1.10.0/gcc/4.8.4/cuda/7.5.7/lib -lhdf5_hl -lhdf5 -lz -ldl ../../../../pamgen/src/libpamgen_extras.a ../../../../pamgen/src/libpamgen.a ../../../../aztecoo/src/libaztecoo.a ../../../../triutils/src/libtriutils.a ../../../../epetra/src/libepetra.a ../../../../shards/src/libshards.a ../../../../zoltan/src/libzoltan.a -lm ../../../../sacado/src/libsacado.a ../../../../teuchos/kokkoscomm/src/libteuchoskokkoscomm.a ../../../../teuchos/kokkoscompat/src/libteuchoskokkoscompat.a ../../../../teuchos/remainder/src/libteuchosremainder.a ../../../../teuchos/numerics/src/libteuchosnumerics.a -L/home/projects/x86-64-haswell/lapack/3.5.0/gcc/4.8.4 -llapack -L/home/projects/x86-64-haswell/blas/20150602/gcc/4.8.4 -lblas ../../../../teuchos/comm/src/libteuchoscomm.a ../../../../teuchos/parameterlist/src/libteuchosparameterlist.a ../../../../teuchos/core/src/libteuchoscore.a ../../../../kokkos/core/src/libkokkoscore.a -lcudart -lcublas -lcufft -lboost_program_options -lboost_system -lmpi_usempi -lmpi_mpifh -lgfortran -lquadmath
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/142Framework: Create GitHub tag for Thyra2016-02-15T17:56:10ZJames WillenbringFramework: Create GitHub tag for Thyra*Created by: mhoemmen*
Please :-) Issue #3 needs this.
*Created by: mhoemmen*
Please :-) Issue #3 needs this.
https://gitlab.osti.gov/jmwille/Trilinos/-/issues/138Add Trilinos Developer Instructions for GitHub Issues and waffle.io2016-02-14T05:24:25ZJames WillenbringAdd Trilinos Developer Instructions for GitHub Issues and waffle.io*Created by: jwillenbring*
@maherou has asked me to write up some instructions for using GitHub Issues and waffle.io. I am going to do this on a Trilinos GitHub wiki page. I am going to use the IDEAS Jira instructions as a guide.
*Created by: jwillenbring*
@maherou has asked me to write up some instructions for using GitHub Issues and waffle.io. I am going to do this on a Trilinos GitHub wiki page. I am going to use the IDEAS Jira instructions as a guide.