Dorsal build problems, 'unknown fortran name mangling'

Something is strange with the installation of your compilers. Could you give me the outputs of the following?

gfortran --version
mpif90 --version
mpif77 --version

Only mpif90 should return something sensible.

Also, try explicitly disabling fortran by setting --with-fc=0 to the configure line in package/petsc.package

Thanks for the quick response!
Output:

gfortran --version
GNU Fortran (GCC) 4.2.3
Copyright (C) 2007 Free Software Foundation, Inc.
mpif90 --version
--------------------------------------------------------------------------
Unfortunately, this installation of Open MPI was not compiled with
Fortran 90 support. As such, the mpif90 compiler is non-functional.
--------------------------------------------------------------------------
mpif77 --version
--------------------------------------------------------------------------
Unfortunately, this installation of Open MPI was not compiled with
Fortran 77 support. As such, the mpif77 compiler is non-functional.
--------------------------------------------------------------------------

I apperently have some problems with Open MPI, suggestions on how to fixe
them?
Thanks for the help in, I am very new to all mac-stuffs so continue to be
explicit. When I try to installed with the suggested change in
petsc.package, the process goes on for a longer time period, but yields a
similar output:

Fetching petsc-3.0.0-p12
Unpacking petsc-3.0.0-p12
Building petsc-3.0.0-p12
============================================================================
=====
            Configuring PETSc to compile on your system
============================================================================
=====
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/config/BuildSystem/config/compile
rs.py:7: DeprecationWarning: the sets module is deprecated
  import sets
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/config/PETSc/package.py:7:
DeprecationWarning: the md5 module is deprecated; use hashlib instead
  import md5
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/config/BuildSystem/script.py:101:
DeprecationWarning: The popen2 module is deprecated. Use the subprocess
module.
  import popen2
============================================================================
===== WARNING! Compiling PETSc with no debugging,
this should only be done for
timing and production runs. All development should
be done when configured using --with-debugging=1
============================================================================
=====
============================================================================
===== Compiling UMFPACK; this may take several minutes
============================================================================
=====
****************************************************************************
*****
        UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for
details):
----------------------------------------------------------------------------
-----------
Error running make on UMFPACK: Could not execute 'cd
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/externalpackages/UMFPACK-5.2/UMFP
ACK;
UMFPACK_INSTALL_DIR=/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-
cxx-opt/lib; export UMFPACK_INSTALL_DIR; make; make clean; mv Lib/*.a
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-cxx-opt/lib; cp
Include/*.h
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-cxx-opt/include; cd
..; cp UFconfig/*.h
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-cxx-opt/include; cd
AMD; mv Lib/*.a
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-cxx-opt/lib; cp
Include/*.h
/Users/tor/Work/FEniCS/src/petsc-3.0.0-p12/darwin10.0.0-cxx-opt/include':
Runaway processRunaway process exceeded time limit of 2500s
****************************************************************************
*****

Failure with exit status: 1
Exit message: There was a problem in build setup for petsc-3.0.0-p12.

Best regards
Tor

On 4/1/10 6:07 , "Harish Narayanan" <email address hidden>
wrote:

> Your question #106141 on Dorsal changed:
> https://answers.launchpad.net/dorsal/+question/106141
>
> Status: Open => Needs information
>
> Harish Narayanan requested for more information:
> Something is strange with the installation of your compilers. Could you
> give me the outputs of the following?
>
> gfortran --version
> mpif90 --version
> mpif77 --version
>
> Only mpif90 should return something sensible.
>
> Also, try explicitly disabling fortran by setting --with-fc=0 to the
> configure line in package/petsc.package

Great, you have now just entered into the seedy underworld of owning a Mac.

To solve this problem, you start the installation process. At some point, the petsc installation will seemingly stall and your computer resources will be used up with nothing noticeable happening. Then, bring up Activity Monitor and kill a task cal umfpack_dl_demo (or something like that), and the installation process will continue unabated (in theory).

On Thu, Apr 01, 2010 at 07:59:44PM -0000, Harish Narayanan wrote:
> Question #106141 on Dorsal changed:
> https://answers.launchpad.net/dorsal/+question/106141
>
> Status: Open => Answered
>
> Harish Narayanan proposed the following answer:
> Great, you have now just entered into the seedy underworld of owning a
> Mac.
>
> To solve this problem, you start the installation process. At some
> point, the petsc installation will seemingly stall and your computer
> resources will be used up with nothing noticeable happening. Then, bring
> up Activity Monitor and kill a task cal umfpack_dl_demo (or something
> like that), and the installation process will continue unabated (in
> theory).

:-)

--
Anders

Thanks for that tip! Killing that process helped the installation process go
on for a few minutes (with the --with-fc=0 as adviced earlier, otherwize it
did not work). However, I now get problems with the libraries
installation...:

Completed building SLEPc libraries
=========================================
Now to install the libraries do: make install
=========================================
Installing SLEPc at /Users/tor/Work/FEniCS
/usr/bin/ranlib: file: /Users/tor/Work/FEniCS/lib/libamd.a(amd_i_dump.o) has
no symbols
/usr/bin/ranlib: file: /Users/tor/Work/FEniCS/lib/libamd.a(amd_l_dump.o) has
no symbols
/usr/bin/ranlib: file:
/Users/tor/Work/FEniCS/lib/libumfpack.a(umf_di_dump.o) has no symbols
/usr/bin/ranlib: file:
/Users/tor/Work/FEniCS/lib/libumfpack.a(umf_dl_dump.o) has no symbols
/usr/bin/ranlib: file:
/Users/tor/Work/FEniCS/lib/libumfpack.a(umf_zi_dump.o) has no symbols
/usr/bin/ranlib: file:
/Users/tor/Work/FEniCS/lib/libumfpack.a(umf_zl_dump.o) has no symbols
making shared libraries in /Users/tor/Work/FEniCS/lib
building libslepc.dylib
=========================================
If using sh/bash, do the following:
  SLEPC_DIR=/Users/tor/Work/FEniCS; export SLEPC_DIR
  unset PETSC_ARCH
If using csh/tcsh, do the following:
  setenv SLEPC_DIR /Users/tor/Work/FEniCS
  unsetenv PETSC_ARCH
Run the following to verify the install (remain in current directory for the
tests):
  make test
Fetching mtl4-beta-1-r6916
--2010-04-02 01:18:01--
http://osl.iu.edu/download/research/mtl/mtl4-beta-1-r6916.tar.gz
Resolving osl.iu.edu (osl.iu.edu)... 129.79.245.239
Connecting to osl.iu.edu (osl.iu.edu)|129.79.245.239|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 868941 (849K) [application/x-gzip]
Saving to: `mtl4-beta-1-r6916.tar.gz'

100%[===================================================>] 868,941
235K/s in 3.6s

2010-04-02 01:18:05 (235 KB/s) - `mtl4-beta-1-r6916.tar.gz' saved
[868941/868941]

Unpacking mtl4-beta-1-r6916
Building mtl4-beta-1-r6916
Fetching scotch_5.1.3
--2010-04-02 01:18:05--
https://gforge.inria.fr/frs/download.php/15601/scotch_5.1.3.tar.gz
Resolving gforge.inria.fr (gforge.inria.fr)... 131.254.249.20
Connecting to gforge.inria.fr (gforge.inria.fr)|131.254.249.20|:443...
connected.
ERROR: cannot verify gforge.inria.fr's certificate, issued by
`/C=NL/O=TERENA/CN=TERENA SSL CA':
  Self-signed certificate encountered.
To connect to gforge.inria.fr insecurely, use `--no-check-certificate'.
Failure with exit status: 5
Exit message: Error fetching scotch_5.1.3.

On 4/1/10 21:59 , "Harish Narayanan" <email address hidden>
wrote:

> Your question #106141 on Dorsal changed:
> https://answers.launchpad.net/dorsal/+question/106141
>
> Status: Open => Answered
>
> Harish Narayanan proposed the following answer:
> Great, you have now just entered into the seedy underworld of owning a
> Mac.
>
> To solve this problem, you start the installation process. At some
> point, the petsc installation will seemingly stall and your computer
> resources will be used up with nothing noticeable happening. Then, bring
> up Activity Monitor and kill a task cal umfpack_dl_demo (or something
> like that), and the installation process will continue unabated (in
> theory).

Thanks!