On Thu, Dec 2, 2010 at 1:59 PM, John R. Cary <span dir="ltr"><<a href="mailto:cary@txcorp.com">cary@txcorp.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On 12/2/2010 12:55 PM, Satish Balay wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'll attempt a build and see how it goes..<br>
</blockquote>
<br>
Thanks. I am doing one now too. I wanted to send configure.log,<br>
but apparently it got overwritten at some later time by running configure<br>
again. I am not sure exactly when this happens, or how one goes back<br>
to getting older logs, so I am rebuilding.<br></blockquote><div><br></div><div>The configure.log is moved to $PETSC_DIR/$PETSC_ARCH/conf/ so that</div><div>multiple builds do not overwrite it.</div><div><br></div><div> Matt</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Anyway, given the pokeyness of the FENs on surveyor, it should be some<br>
time before midnight!<br>
<br>
John<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
satish<br>
<br>
On Thu, 2 Dec 2010, Matthew Knepley wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We always always always always need configure.log.<br>
<br>
Matt<br>
<br>
On Thu, Dec 2, 2010 at 8:41 AM, John R. Cary<<a href="mailto:cary@txcorp.com" target="_blank">cary@txcorp.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am trying to link facets on a FEN of <a href="http://surveyor.alcf.anl.gov" target="_blank">surveyor.alcf.anl.gov</a>. It ends<br>
with the error,<br>
<br>
/gpfs/home/projects/facets/surveyor/contrib-xlc-9.0/petsc-3.1-p4-ser/lib/libsuperlu_4.0.a(dldperm.o):<br>
In function `dldperm':<br>
/gpfs/home/cary/facetspkgs/builds/petsc-3.1-p4/ser/externalpackages/SuperLU_4.0/SRC/dldperm.c:127:<br>
undefined reference to `mc64id_'<br>
/gpfs/home/cary/facetspkgs/builds/petsc-3.1-p4/ser/externalpackages/SuperLU_4.0/SRC/dldperm.c:134:<br>
undefined reference to `mc64ad_'<br>
<br>
which indicates that the SuperLU compiled with PETSc did<br>
not get the fortran underscoring flag correct (which should<br>
be no underscore with xlf). nm shows<br>
<br>
login1.surveyor$ nm<br>
/gpfs/home/projects/facets/surveyor/contrib-xlc-9.0/petsc-3.1-p4-ser/lib/libsuperlu_4.0.a<br>
| grep mc64<br>
U mc64ad_<br>
U mc64id_<br>
mc64ad.o:<br>
0000000000000018 D mc64ad<br>
0000000000000030 D mc64bd<br>
0000000000000048 D mc64dd<br>
0000000000000060 D mc64ed<br>
0000000000000078 D mc64fd<br>
0000000000000000 D mc64id<br>
00000000000000c0 D mc64qd<br>
0000000000000090 D mc64rd<br>
00000000000000a8 D mc64sd<br>
00000000000000d8 D mc64ud<br>
00000000000000f0 D mc64wd<br>
U mc64ad_<br>
U mc64id_<br>
<br>
that the underscored symbol is being called, but the<br>
underscore-free symbol is what was defined.<br>
<br>
My PETSc configure line was<br>
<br>
#!/bin/sh<br>
/gpfs/home/cary/facetspkgs/builds-surveyor-xlc/facetspkgs/petsc-3.1-p4/ser/configure<br>
\<br>
--prefix=/gpfs/home/projects/facets/surveyor/contrib-xlc-9.0/petsc-3.1-p4-ser<br>
\<br>
--with-mpi=0 \<br>
--with-debugging=0 \<br>
--with-x=0 \<br>
--with-cc='xlc_r' \<br>
--with-cxx='xlC_r' \<br>
--with-fc='xlf_r' \<br>
--COPTFLAGS='-O2 -g' \<br>
--download-superlu \<br>
--with-lapack-lib=/home/projects/facets/intrepid/contrib/lapack-ser/lib/liblapack.a<br>
\<br>
--with-blas-lib=/home/projects/facets/intrepid/contrib/lapack-ser/lib/libblas.a<br>
\<br>
PETSC_DIR=/gpfs/home/cary/facetspkgs/builds-surveyor-xlc/facetspkgs/petsc-3.1-p4/ser<br>
\<br>
PETSC_ARCH=facets-ser \<br>
--CFLAGS='-q64 -qlanglvl=redefmac' \<br>
--CXXFLAGS='-q64 -qlanglvl=redefmac' \<br>
--FFLAGS='-q64 -qextname=flush' \<br>
--with-shared=1<br>
<br>
so I think that PETSc had enough info to figure out the underscoring.<br>
Perhaps this is a bug.<br>
<br>
But regardless, is there a workaround?<br>
<br>
Thx....John<br>
<br>
</blockquote>
<br>
<br>
<br>
</blockquote></blockquote>
<br>
</blockquote></div><br><br clear="all"><br>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>