[Trilinos-Users] Building trilinos-10.0.5 on Intrepid (BGP)

[John R Cary]

So I finally got trilinos to build in parallel on BGP, but I had to do several
things:

1. I had to patch both the code in one place (using std) to resolve
and ambiguity, and to figure out the Fortran demangling.  I had tried to do

 SET(F77_FUNC_DEFAULT "(name,NAME) name")
 SET(F77_FUNC__DEFAULT "(name,NAME) name")

but I could not seem to override what was in TrilinosFortranMangling.cmake.

My patch file is attached.  (I as also unable to use the variable,
CMAKE_FORTRAN_COMPILER_ID, which I thought should exist.  Instead I
used CMAKE_C_COMPILER_ID.

2. I created a toolchain file (attached).  I had to add the stanza
# Exit codes as needed for cross-compile
set(HAVE_GCC_ABI_DEMANGLE_EXITCODE 0)
set(HAVE_TEUCHOS_BLASFLOAT_EXITCODE 0)
set(CXX_COMPLEX_BLAS_WORKS_EXITCODE 0)

to stop make from complaining that Trilinos was using TryRun in
a cross-compile situation.


Question: in the pre-10 Trilinos, I could get the fortran dependency
libs by grepping them out of, e.g., Makefile.export.aztecoo.  Now 
these do not seem to be in any of the Makefile.export.* files.  Is
there another way to get them?

Thx.....John Cary




-------------- next part --------------
A non-text attachment was scrubbed...
Name: trilinos-10.0.5.patch
Type: application/octet-stream
Size: 1190 bytes
Desc: not available
Url : https://software.sandia.gov/pipermail/trilinos-users/attachments/20100328/6daad684/attachment.obj 
-------------- next part --------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: Toolchain-BlueGeneP-xl.cmake
Type: application/octet-stream
Size: 1414 bytes
Desc: not available
Url : https://software.sandia.gov/pipermail/trilinos-users/attachments/20100328/6daad684/attachment-0001.obj 
-------------- next part --------------







On Feb 16, 2010, at 6:42 PM, John R. Cary wrote:

> Attached is my configure failure on BGP for the compute nodes.
> 
> I am sure everyone knows, but this is a cross-compile situation.
> 
> Upon reading the error messages, it sounded like I could
> just define these in CMakeCache.txt
>  HAVE_GCC_ABI_DEMANGLE_EXITCODE
>  HAVE_TEUCHOS_BLASFLOAT_EXITCODE
>  CXX_COMPLEX_BLAS_WORKS_EXITCODE
> 
> all to 0.  So I did that and it did configure and is building.
> 
> I then see:
> 
> System is unknown to cmake, create:
> Platform/BlueGeneP to use this system, please send your config file to cmake at www
> .cmake.org so it can be added to cmake
> 
> but I am not sure what to do?
> 
> Is there some more automatic/convenient way to do this
> other then editing CMakeCache.txt?
> 
> Thanks....John Cary
> 
> 
> 
> 
> 
> <configure.out>