Menu
▾
▴
libmesh-users
|
From: Leopold P. A. <le...@wo...> - 2003-11-06 12:17:39
|
Hi, I'm new in libmesh and I'm having a problem trying to compile it. I'm trying to compile libmesh libmesh-0.4.1-rc2 in a debian woody system. I have installed petsc, mpi. Howeber whe I run configure with: ./configure --prefix=/usr --enable-mpi --enable-petsc --enable-laspack I have this message: [...] checking for /include/petsc.h... no checking for /include/mpi.h... no checking for /lib/libmpich.a... no [...] In general, in a debian system this files are in: /usr/include/petsc/petsc.h /usr/include/mpi/mpi.h /usr/lib/mpich/lib/libmpich.a How I can to tell to configure that look in that places? Best regards, Leo |
|
From: Benjamin S. K. <be...@cf...> - 2003-11-06 15:51:11
|
On most systems where PETSc is installed from source the environment variables PETSC_DIR and PETSC_ARCH are used to describe the installation. For example, on my machine, the values for these variables are: hactar(4)$ echo $PETSC_DIR /usr/local/petsc/petsc-2.1.5 hactar(5)$ echo $PETSC_ARCH linux so, for your system I think this should work: export PETSC_DIR=/usr export PETSC_ARCH=linux and re-run configure. We currently do not support a 'make install' target, so at the moment the --prefix=/usr command line argument will have no effect and may be omitted. Let me know if you have any more trouble. I know of another user (right, Denis?) who has exactly your configuration working, so it is certainly possible. I personally don't have access to a Debian machine with the PETSc packages installed, so my troubleshooting is a little limited... -Ben |
|
From: Leopold P. A. <le...@wo...> - 2003-11-06 16:15:20
|
A Dijous 06 Novembre 2003 16:51, Benjamin S. Kirk va escriure:
> On most systems where PETSc is installed from source the environment
> variables PETSC_DIR and PETSC_ARCH are used to describe the
> installation. For example, on my machine, the values for these
> variables are:
>
> hactar(4)$ echo $PETSC_DIR
> /usr/local/petsc/petsc-2.1.5
> hactar(5)$ echo $PETSC_ARCH
> linux
>
>
> so, for your system I think this should work:
>
> export PETSC_DIR=/usr
> export PETSC_ARCH=linux
>
> and re-run configure.
>
> We currently do not support a 'make install' target, so at the moment
> the --prefix=/usr command line argument will have no effect and may be
> omitted.
>
> Let me know if you have any more trouble. I know of another user
> (right, Denis?) who has exactly your configuration working, so it is
> certainly possible. I personally don't have access to a Debian machine
> with the PETSc packages installed, so my troubleshooting is a little
> limited...
>
> -Ben
Hi Ben,
thank's for the answer. Sadly I say htat I have some trouble.... :-(
lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ export PETSC_DIR=/usr
lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ export PETSC_ARCH=linux
lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ ./configure --enable-mpi
--enable-petsc --enable-laspack
.....
checking for /usr/include/petsc.h... no
checking for /include/mpi.h... no
checking for /lib/libmpich.a... no
.....
The question is the configure checks for include/petsch.h, and no, in a debian
system in general in the /usr/include/ there are the directories with the
name of the directory and inside the headers, so your /usr/include/ has some
kind or ordre. I think that it's necessary to change the aclocal.m4 in the
line 505:
......
AC_DEFUN(CONFIGURE_PETSC,
[
AC_CHECK_FILE($PETSC_DIR/include/petsc.h,
PETSC_H_PATH=$PETSC_DIR/include/petsc.h)
if (test -r $PETSC_DIR/include/petsc.h) ; then
... I think that this macro is not good. You think that all the tditributions
of petsc put the petsc.h header in a include directory, and for example
debian doens't.
So, probably is necessary to change this macro, and re-run autoconf to create
the configure file. IMO. But I have tried to modify it and I have lost :-(
Leo
Leo
|
|
From: danilovdenis <dan...@ya...> - 2003-11-06 19:16:53
|
>Let me know if you have any more trouble. I know of another user >(right, Denis?) who has exactly your configuration working, so it is >certainly possible. I personally don't have access to a Debian machine >with the PETSc packages installed, so my troubleshooting is a little >limited... Hi, Yes, I have libmesh working on debian--woody. There are two things related to petsc. First you have to set environment variables PETSC_DIR and PETSC_ARCH. As Jens said PETSC_DIR="/usr/lib/petsc" and PETSC_ARCH="linux". Second, the petsc in debian package is *dynamically* linked with mpi libraries and I had to add them manually to FLIBS in Make.common after configuration. Ben, would be variables LIBS or LDFLAGS the better place for this? I thought, that "F" means fortran in FLIBS. Denis |
|
From: Jens O. <oe...@st...> - 2003-11-06 16:23:35
|
Hi, I am running exactly the same installation (woody with petsc) and I set PETSC_DIR and PETSC_ARCH in my .bashrc to: export PETSC_DIR="/usr/lib/petsc" export PETSC_ARCH="linux" I also made a backport from petsc in Debian unstable (version 2.1.6) to woody, which is not very difficult. Let me know if there are any problems. Regards Jens. On Thu, 6 Nov 2003 13:15:11 +0100 Leopold Palomo Avellaneda <le...@wo...> wrote: > Hi, > > I'm new in libmesh and I'm having a problem trying to compile it. I'm > trying to compile libmesh libmesh-0.4.1-rc2 in a debian woody system. > I have installed petsc, mpi. Howeber whe I run configure with: > > ./configure --prefix=/usr --enable-mpi --enable-petsc --enable-laspack > > I have this message: > [...] > checking for /include/petsc.h... no > checking for /include/mpi.h... no > checking for /lib/libmpich.a... no > [...] > > In general, in a debian system this files are in: > /usr/include/petsc/petsc.h > /usr/include/mpi/mpi.h > /usr/lib/mpich/lib/libmpich.a > > How I can to tell to configure that look in that places? > > Best regards, > > Leo > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > Does SourceForge.net help you be more productive? Does it > help you create better code? SHARE THE LOVE, and help us help > YOU! Click Here: http://sourceforge.net/donate/ > _______________________________________________ > Libmesh-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libmesh-users -- Clothes make the man. Naked people have little or no influence on society. -- Mark Twain |
|
From: Leopold P. A. <le...@wo...> - 2003-11-06 16:35:05
|
A Dijous 06 Novembre 2003 17:23, Jens Oeser va escriure: > Hi, > > I am running exactly the same installation (woody with petsc) and I set > PETSC_DIR and PETSC_ARCH in my .bashrc to: > > export PETSC_DIR="/usr/lib/petsc" > export PETSC_ARCH="linux" > > I also made a backport from petsc in Debian unstable (version 2.1.6) to > woody, which is not very difficult. Let me know if there are any > problems. > > Regards > Jens. Hi, thank's. I have tried it and not it works. How about to put it in a FAQ, README, etc. Howeber I have found a new error now. lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ make Makefile:71: warning: overriding commands for target `/rhome/lepalom/Finite' Makefile:62: warning: ignoring old commands for target `/rhome/lepalom/Finite' Compiling C++ (in optimized mode) src/base/dof_map.C... g++: cannot specify -o with -c or -S and multiple compilations make: *** [src/base/dof_map.i686-pc-linux-gnu.o] Error 1 I have found that it's not a problem with the compiler. It's about some empty var in the Makefiles, so the compiler had an error. The complete configure output is: epalom@e01:~/Finite element/libmesh-0.4.1-rc2$ export PETSC_DIR="/usr/lib/ petsc" lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ export PETSC_ARCH="linux" lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ ./configure --enable-mpi --enable-petsc --enable-laspack --------------------------------------------- ----------- Configuring libMesh ------------- --------------------------------------------- checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking for g++... g++ checking for C++ compiler default output... a.out checking whether the C++ compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking for gcc... gcc checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed <<< C++ compiler is gcc-2.95 >>> <<< Configuring library for broken iostream >>> checking how to run the C++ preprocessor... g++ -E checking for egrep... grep -E 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 short int... yes checking size of short int... 2 checking for int... yes checking size of int... 4 checking for long int... yes checking size of long int... 4 checking for float... yes checking size of float... 4 checking for double... yes checking size of double... 8 checking for void *... yes checking size of void *... 4 checking getopt.h usability... yes checking getopt.h presence... yes checking for getopt.h... yes checking whether the compiler implements namespaces... yes checking whether the compiler has locale... no checking whether the compiler has stringstream... yes checking hash_map usability... yes checking hash_map presence... yes checking for hash_map... yes checking hash_set usability... yes checking hash_set presence... yes checking for hash_set... yes checking zlib.h usability... no checking zlib.h presence... no checking for zlib.h... no <<< Configuring library with AMR support >>> <<< Configuring library with expensive data structures enabled >>> checking rpc/rpc.h usability... yes checking rpc/rpc.h presence... yes checking for rpc/rpc.h... yes <<< Configuring library with XDR support >>> <<< Configuring library with real number support >>> <<< Configuring library with reference counting support >>> checking for ./contrib/netcdf/lib/i686-pc-linux-gnu/libnetcdf.a... no checking for ./contrib/netcdf/include/netcdf.h... no --------------------------------------------- ----- Configuring for optional packages ----- --------------------------------------------- checking for ./contrib/sfcurves/sfcurves.h... yes ./configure: line 7513: test: /rhome/lepalom/Finite: binary operator expected checking for ./contrib/gzstream/gzstream.h... yes ./configure: line 7564: test: /rhome/lepalom/Finite: binary operator expected checking for ./contrib/tecplot/lib/i686-pc-linux-gnu/tecio.a... yes checking for ./contrib/tecplot/include/TECIO.h... yes ./configure: line 7693: test: too many arguments checking for ./contrib/laspack/lastypes.h... yes ./configure: line 7746: test: /rhome/lepalom/Finite: binary operator expected checking for /usr/lib/petsc/include/petsc.h... yes checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes checking how to get verbose linking output from g77... -v checking for Fortran 77 libraries... -L/usr/lib/gcc-lib/i386-linux/2.95.4 -lg2c -lm <<< Configuring library with PETSc version 2.1.3 support >>> checking for ./contrib/metis/Lib/metis.h... yes ./configure: line 8530: test: /rhome/lepalom/Finite: binary operator expected checking for ./contrib/parmetis/Lib/parmetis.h... yes ./configure: line 8581: test: /rhome/lepalom/Finite: binary operator expected checking for doxygen... /usr/bin/doxygen checking for dot... no ---------------------------------------------- --- Done configuring for optional packages --- ---------------------------------------------- checking for perl... /usr/bin/perl configure: creating ./config.status config.status: creating Make.common config.status: creating include/mesh_config.h configure: creating ./config.status config.status: creating Make.common config.status: creating doc/Doxyfile config.status: creating include/mesh_config.h config.status: include/mesh_config.h is unchanged --------------------------------------------- --------- Done Configuring libMesh ---------- --------------------------------------------- Leo |
|
From: danilovdenis <dan...@ya...> - 2003-11-06 19:16:53
|
>I have tried it and not it works. How about to put it in a FAQ, README, etc. >Howeber I have found a new error now. > >lepalom@e01:~/Finite element/libmesh-0.4.1-rc2$ make >Makefile:71: warning: overriding commands for target `/rhome/lepalom/Finite' >Makefile:62: warning: ignoring old commands for target `/rhome/lepalom/Finite' >Compiling C++ (in optimized mode) src/base/dof_map.C... >g++: cannot specify -o with -c or -S and multiple compilations >make: *** [src/base/dof_map.i686-pc-linux-gnu.o] Error 1 ... >./configure: line 7513: test: /rhome/lepalom/Finite: binary operator expected Here is a "bad" name of working directory. For example "Finite_element", i.e. without whitespace will be more better... Denis. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X