1) With any error report you MUST send configure.log, or we know nothing about your build. Send<div> it to <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a></div><div><br></div><div>2) Where are the error lines from UMFPack coming from? Not from the PETSc build.</div>
<div><br></div><div>3) I have no idea why Dolfin segfaults. YOu should mail the Dolfin list</div><div><br></div><div> Matt<br><br><div class="gmail_quote">On Fri, Jul 9, 2010 at 4:57 PM, Frantisek Fridrich <span dir="ltr"><<a href="mailto:frafridr@gmail.com">frafridr@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello.<br>
<br>
Please could anybody help me?<br>
<br>
I compiled PETSc 3.1-p3 in Scientific Linux 5, gcc-4.4.4 with options:<br>
=========================================================== beg<br>
--prefix=${P_petsc_INSTALL} \<br>
--with-external-packages-dir=${P_extpckg_INSTALL} \<br>
--PETSC_ARCH=${PETSC_ARCH} \<br>
--PETSC_DIR=${PETSC_DIR} \<br>
--with-clanguage=c++ \<br>
--with-c-support=yes \<br>
--with-shared=yes \<br>
--with-large-file-io=yes \<br>
--CFLAGS=${CFLAGS} \<br>
--CXXFLAGS=${CXXFLAGS} \<br>
--FFLAGS=${FCFLAGS} \<br>
--with-ar=ar \<br>
--AR_FLAGS=cr \<br>
--with-ranlib=ranlib \<br>
--COPTFLAGS=${COPTFLAGS} \<br>
--CXXOPTFLAGS=${CXXOPTFLAGS} \<br>
--FOPTFLAGS=${FOPTFLAGS} \<br>
--with-mpi-dir=${P_MPI_INSTALL} \<br>
--with-mpi-shared=yes \<br>
--with-spooles=yes \<br>
--download-spooles=yes \<br>
--with-blas-lapack-dir=${ATLAS} \<br>
--with-blacs=yes \<br>
--download-blacs=yes \<br>
--with-parmetis=yes \<br>
--with-parmetis-dir=${P_parmetis_INSTALL} \<br>
--with-scalapack=yes \<br>
--download-scalapack=yes \<br>
--with-mumps=yes \<br>
--download-mumps=yes \<br>
--with-hypre=yes \<br>
--with-hypre-dir=${P_hypre_INSTALL} \<br>
--with-umfpack=yes \<br>
--download-umfpack=yes \<br>
=========================================================== end<br>
<br>
I got 1600 lines of the following warnings:<br>
=========================================================== beg<br>
../Source/umf_analyze.c: In function ‘umf_i_analyze’:<br>
../Source/umf_analyze.c:94: warning: ignoring #pragma ivdep<br>
../Source/umf_analyze.c:581: warning: ignoring #pragma novector<br>
../Source/umf_analyze.c: In function ‘umf_l_analyze’:<br>
../Source/umf_analyze.c:94: warning: ignoring #pragma ivdep<br>
<br>
<br>
../Source/umf_blas3_update.c: In function ‘umfdi_blas3_update’:<br>
../Source/umf_blas3_update.c:81: warning: ignoring #pragma ivdep<br>
../Source/umf_blas3_update.c:100: warning: passing argument 1 of<br>
‘dtrsm_’ discards qualifiers from pointer target type<br>
../Source/cholmod_blas.h:243: note: expected ‘char *’ but argument is<br>
of type ‘const char *’<br>
../Source/umf_blas3_update.c:100: warning: passing argument 2 of<br>
‘dtrsm_’ discards qualifiers from pointer target type<br>
../Source/cholmod_blas.h:243: note: expected ‘char *’ but argument is<br>
of type ‘const char *’<br>
<br>
<br>
../Source/umfpack_report_info.c: In function ‘umfpack_di_report_info’:<br>
../Source/umfpack_report_info.c:403: warning: passing argument 1 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
../Source/umfpack_report_info.c:403: warning: passing argument 2 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
../Source/umfpack_report_info.c:405: warning: passing argument 1 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
<br>
<br>
../Source/umf_blas3_update.c:152: warning: ignoring #pragma ivdep<br>
../Source/umf_create_element.c: In function ‘copy_column’:<br>
../Source/umf_create_element.c:31: warning: ignoring #pragma ivdep<br>
../Source/umf_create_element.c: In function ‘umfdl_create_element’:<br>
<br>
../Source/umfpack_report_info.c:403: warning: passing argument 1 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
../Source/umfpack_report_info.c:403: warning: passing argument 2 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
../Source/umfpack_report_info.c:405: warning: passing argument 1 of<br>
‘print_ratio’ discards qualifiers from pointer target type<br>
../Source/umfpack_report_info.c:33: note: expected ‘char *’ but<br>
argument is of type ‘const char *’<br>
<br>
umfpack_zl_demo.c:547: warning: format ‘%ld’ expects type ‘long int’,<br>
but argument 2 has type ‘long long int’<br>
umfpack_zl_demo.c:547: warning: format ‘%ld’ expects type ‘long int’,<br>
but argument 3 has type ‘long long int’<br>
<br>
umfpack_zl_demo.c:719: warning: passing argument 1 of ‘error’ discards<br>
qualifiers from pointer target type<br>
umfpack_zl_demo.c:75: note: expected ‘char *’ but argument is of type<br>
‘const char *’<br>
umfpack_zl_demo.c:728: warning: passing argument 1 of ‘error’ discards<br>
qualifiers from pointer target type<br>
umfpack_zl_demo.c:75: note: expected ‘char *’ but argument is of type<br>
‘const char *’<br>
make[1]: [run] Error 1 (ignored)<br>
make[1]: [run] Error 1 (ignored)<br>
make[1]: [run] Error 1 (ignored)<br>
make[1]: [run] Error 1 (ignored)<br>
********End of Output of running make on UMFPACK *******<br>
=========================================================== end<br>
<br>
When running DOLFIN 0.9.8 demos I got error:<br>
=========================================================== beg<br>
Newton iteration 8: r (abs) = 1.509e-14 (tol = 1.000e-10) r (rel)<br>
= 3.674e-15 (tol = 1.000e-09)<br>
Newton solver finished in 8 iterations and 8 linear solver iterations.<br>
Plot active, press 'q' to continue.<br>
[0]PETSC ERROR:<br>
------------------------------------------------------------------------<br>
[0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,<br>
probably memory access out of range<br>
[0]PETSC ERROR: Try option -start_in_debugger or -on_error_attach_debugger<br>
[0]PETSC ERROR: or see<br>
<a href="http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC" target="_blank">http://www.mcs.anl.gov/petsc/petsc-as/documentation/troubleshooting.html#Signal[0]PETSC</a><br>
ERROR: or try <a href="http://valgrind.org" target="_blank">http://valgrind.org</a> on GNU/linux and Apple Mac OS X to<br>
find memory corruption errors<br>
[0]PETSC ERROR: likely location of problem given in stack below<br>
[0]PETSC ERROR: --------------------- Stack Frames<br>
------------------------------------<br>
[0]PETSC ERROR: Note: The EXACT line numbers in the stack are not available,<br>
[0]PETSC ERROR: INSTEAD the line number of the start of the function<br>
[0]PETSC ERROR: is given.<br>
[0]PETSC ERROR: --------------------- Error Message<br>
------------------------------------<br>
[0]PETSC ERROR: Signal received!<br>
[0]PETSC ERROR:<br>
------------------------------------------------------------------------<br>
[0]PETSC ERROR: Petsc Release Version 3.1.0, Patch 3, Fri Jun 4<br>
15:34:52 CDT 2010<br>
[0]PETSC ERROR: See docs/changes/index.html for recent updates.<br>
[0]PETSC ERROR: See docs/faq.html for hints about trouble shooting.<br>
[0]PETSC ERROR: See docs/index.html for manual pages.<br>
[0]PETSC ERROR:<br>
------------------------------------------------------------------------<br>
[0]PETSC ERROR: Unknown Name on a linux-gnu named juniper by fridrich<br>
Fri Jul 9 11:27:30 2010<br>
[0]PETSC ERROR: Libraries linked from<br>
/home/rose/OpenMPI/openmpi-1.4.2/utils/petsc-3.1-p3/lib<br>
[0]PETSC ERROR: Configure run at Thu Jul 8 19:49:50 2010<br>
[0]PETSC ERROR: Configure options<br>
--prefix=/home/rose/OpenMPI/openmpi-1.4.2/utils/petsc-3.1-p3<br>
--with-external-packages-dir=/home/rose/OpenMPI/openmpi-1.4.2/utilsRepo/petsc-3.1-p3/petscUtilsRepo<br>
--PETSC_ARCH=linux-gnu<br>
--PETSC_DIR=/home/rose/OpenMPI/openmpi-1.4.2/utilsRepo/petsc-3.1-p3/petsc-3.1-p3<br>
--with-clanguage=c++ --with-c-support=yes --with-shared=yes<br>
--with-large-file-io=yes --CFLAGS= -Wall -march=opteron -m64 -O2<br>
-fno-reorder-blocks -fno-reorder-functions -pipe -fPIC --CXXFLAGS=<br>
-Wall -march=opteron -m64 -O2 -fno-reorder-blocks<br>
-fno-reorder-functions -pipe -fPIC --FFLAGS= -Wall -march=opteron -m64<br>
-O2 -fno-reorder-blocks -fno-reorder-functions -pipe -fPIC<br>
--with-ar=ar --AR_FLAGS=cr --with-ranlib=ranlib --COPTFLAGS= -O2<br>
-fno-reorder-blocks -fno-reorder-functions --CXXOPTFLAGS= -O2<br>
-fno-reorder-blocks -fno-reorder-functions --FOPTFLAGS= -O2<br>
-fno-reorder-blocks -fno-reorder-functions<br>
--with-mpi-dir=/home/rose/OpenMPI/openmpi-1.4.2/install<br>
--with-mpi-shared=yes --with-spooles=yes --download-spooles=yes<br>
--with-blas-lapack-dir=/home/rose/OpenMPI/openmpi-1.4.2/utils/atlas-3.9.24/lib<br>
--with-blacs=yes --download-blacs=yes --with-parmetis=yes<br>
--with-parmetis-dir=/home/rose/OpenMPI/openmpi-1.4.2/utils/ParMetis-3.1.1<br>
--with-scalapack=yes --download-scalapack=yes --with-mumps=yes<br>
--download-mumps=yes --with-hypre=yes<br>
--with-hypre-dir=/home/rose/OpenMPI/openmpi-1.4.2/utils/hypre-2.6.0b<br>
--with-umfpack=yes --download-umfpack=yes<br>
[0]PETSC ERROR:<br>
------------------------------------------------------------------------<br>
[0]PETSC ERROR: User provided function() line 0 in unknown directory<br>
unknown file<br>
--------------------------------------------------------------------------<br>
=========================================================== end<br>
<br>
Thank you for response.<br>
<font color="#888888">Frantisek<br>
</font></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>
</div>