[Dune] Problem with the installation

[Christian Engwer]

Hi Mauro,

please have a look at the introduction in the installation notes
  http://www.dune-project.org/doc/installation-notes.html
the first half your questions should be answered there.

Second you will have to install a fortran compiler. Sadly this is
necessary to link to fortran libs like libblas.

For the duneproject script. It uses the dunecontrol mechanism to
search for other dune modules. The default search path is "." +
recursion. If you want to change this you have specify
DUNE_CONTROL_PATH (see e.g. the buildsystemhowto).

Cheers
Christian

On Mon, May 07, 2012 at 12:00:40PM +0200, Mauro Pagani wrote:
> 
> Hi, I contact you for a problem about the installation of DUNE. I try to configure modules, but erase a problem with Fortran 77. I see something on the site, but I don't understand how to solve this problem. Can you help me?..
> 
> 
> ___________________________________________________________________________
> The code is:
> 
> [root at Mauro mauro]# cd Scaricati
> [root at Mauro Scaricati]# cd dune-common-2.1.1
> [root at Mauro dune-common-2.1.1]# ./configure
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking how to create a pax tar archive... gnutar
> checking how to create a pax tar archive... (cached) gnutar
> checking for inkscape... no
> checking for doxygen... no
> checking for latex... no
> checking for bibtex... no
> checking for dvipdf... dvipdf
> checking for dvips... no
> checking for wml... no
> checking for dot... no
> checking for perl... perl
> checking for convert... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for style of include used by make... GNU
> checking for gcc... gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables... 
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ISO C89... none needed
> checking dependency style of gcc... gcc3
> checking dependency style of gcc... (cached) gcc3
> checking how to run the C preprocessor... gcc -E
> checking for g++... g++
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... gcc3
> checking dependency style of g++... (cached) gcc3
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for xlf... no
> checking for f77... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for xlf90... no
> checking for f90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for xlf95... no
> checking for f95... no
> checking for fort... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgfortran... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking whether we are using the GNU Fortran 77 compiler... no
> checking whether  accepts -g... no
> checking for gfortran... no
> checking for g95... no
> checking for xlf95... no
> checking for f95... no
> checking for fort... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgfortran... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... no
> checking for xlf90... no
> checking for f90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for g77... no
> checking for xlf... no
> checking for f77... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking whether we are using the GNU Fortran compiler... no
> checking whether  accepts -g... no
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking how to print strings... printf
> checking for a sed that does not truncate output... /bin/sed
> checking for grep that handles long lines and -e... /bin/grep
> checking for egrep... /bin/grep -E
> checking for fgrep... /bin/grep -F
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 1572864
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
> checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for dlltool... no
> checking how to associate runtime and link libraries... printf %s\n
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for strip... strip
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for sysroot... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking for dlfcn.h... yes
> checking for objdir... .libs
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC -DPIC
> checking if gcc PIC flag -fPIC -DPIC works... yes
> checking if gcc static flag -static works... no
> checking if gcc supports -c -o file.o... yes
> checking if gcc supports -c -o file.o... (cached) yes
> checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... no
> checking whether to build static libraries... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for ld used by g++... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
> checking for g++ option to produce PIC... -fPIC -DPIC
> checking if g++ PIC flag -fPIC -DPIC works... yes
> checking if g++ static flag -static works... no
> checking if g++ supports -c -o file.o... yes
> checking if g++ supports -c -o file.o... (cached) yes
> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
> checking dynamic linker characteristics... (cached) GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking for ranlib... (cached) ranlib
> checking how to get verbose linking output from ... configure: WARNING: compilation failed
> 
> checking for Fortran 77 libraries of ... 
> checking for dummy main to link with Fortran 77 libraries... none
> checking for Fortran 77 name-mangling scheme... configure: error: in `/home/mauro/Scaricati/dune-common-2.1.1':
> configure: error: cannot compile a simple Fortran program
> See `config.log' for more details
> 
> __________________________________________________________________________________________________________________
> 
> 
> And even if I don't configure the modules, I manage to build a new project with  the command ./duneproject. But when I try to open it terminal says:
> 
> ______________________________________________________________________-
> 
> [root at Mauro dune-common-2.1.1]# cd bin
> [root at Mauro bin]# ./duneproject PrimaProva
> 
> == Dune project/module generator ==
> 
> duneproject will assist you in the creation of a new Dune application.
> During this process a new directory with the name of your project will be
> created. This directory will hold all configuration and Makefiles and a
> simple example application.
> 
> ERROR: could not find module dune-common,
>        module is also unknown to pkg-config.
>        Maybe you need to adjust PKG_CONFIG_PATH!
>        dune-common is required by PrimaProva
> 
> ____________________________________________________________________________
> 
> Is it a problem of configuration or anything else?..
> 
> Thank you for your help.
> 
> Mauro Pagani
> 
> 
>  		 	   		  

> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune