On 07/21/14 17:14, wireless wrote:
Howdy OPM folks,
I was finally able to get a clean build on OPM (et. al.) ?
Here is what has built (correctly?) on Gentoo:
dev-cpp/eigen-3.1.3
app-admin/eselect-lapack-0.1
app-admin/eselect-blas-0.1
sci-libs/amd-2.2.0
sci-libs/blas-reference-20070226
virtual/blas-1.0
sci-libs/umfpack-5.2.0
sci-libs/superlu-4.3
sci-libs/lapack-reference-3.1.1-r1
virtual/lapack-3.1
sci-libs/dune-common-2.3.1
sci-libs/dune-istl-2.3.1
sci-physics/opm-core-2013.10
sci-physics/opm-autodiff-2013.10
So now how do I test these packages, one at a time?
Is there some test vectors I can run to set the entire package?
I a previous thread, re-naming and re-organizing the modules is
being discuss. Might testing the components individually
or in some logically organized modules be a consideration, as
the name changes are explored?
I anxiously await testing suggestions.
Once these modules are verified to work, I'll be posting the ebuilds
(gentoo software packages) up on the net for others to enjoy.
sincerely,
James Horton
Gentoo Hack
OH, I did not mention these new items too, which all compile
successfully:
sci-physics/opm-polymer-2013.10
sci-physics/opm-material-2013.10
sci-libs/dune-geometry-2.3.1
sci-libs/dune-grid-2.3.1-r1
sci-physics/dune-cornerpoint-2013.10
sci-physics/opm-porsol-2013.10
sci-physics/opm-upscaling-2013.10
Suggestions as to Testing semantics to verify these packages would be
keenly appreciated.
James
James
_______________________________________________
Opm mailing list
[email protected]
http://www.opm-project.org/mailman/listinfo/opm
