On Tue, 20 Sep 2011, Minq Q wrote:
> When I tried to config libmesh with trilinos (version 4847) I got this error:
>
> checking for
> /prog/trilinos/10.4.1/mpi/opt/include/Makefile.export.Trilinos... yes
> <<< Configuring library with Trilinos 10 support >>>
> checking for /prog/trilinos/10.4.1/mpi/opt/include/AztecOO_config.h... yes
> <<< Configuring library with AztecOO support >>>
> checking for /prog/trilinos/10.4.1/mpi/opt/include/NOX_Config.h... yes
> <<< Configuring library with NOX support >>>
> checking for /prog/trilinos/10.4.1/mpi/opt/include/Makefile.export.aztecoo...
> no
> checking for
> /prog/trilinos/10.4.1/mpi/opt/packages/aztecoo/Makefile.export.aztecoo... no
>
> Should it be
> checking for /prog/trilinos/10.4.1/mpi/opt/include/Makefile.export.AztecOO...
> instead of
> ...aztecoo ?
Hmm... the new system is supposed to work by checking for
Makefile.export.Trilinos (for Trilinos 10 support) and then if that's
not found checking for Makefile.export.{aztecoo,nox} (which really are
lower case, for Trilinos 8 and 9 support). We just must have
forgotten to put the latter check in a conditional - that should be
easy to fix.
It should be working, anyways, even if the configure log messages are
misleading, right?
---
Roy
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Libmesh-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
