installing fenics via dorsal in opensuse
Dear all,
I need to install fenics into one of our servers running with opensuse 10
After some dependency problems, I am stuck with that problem:
-------
...
Processing enabled package: PyTrilinos
-- Found PythonInterp: /usr/bin/python2.5 (Required is at least version "2.2")
CMake Error at packages/
Required NumPy python module not found
Call Stack (most recent call first):
packages/
CMake Error at packages/
SWIG was not found. Please specify Swig executable location
Call Stack (most recent call first):
packages/
-- Configuring incomplete, errors occurred!
-------
Question: Should first the numpy installed (in standard repositories exists no package under the name numpy) ?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- DOLFIN Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Andre Massing
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
On 07/07/2011 01:41 PM, B. Emek Abali wrote:
> New question #164054 on DOLFIN:
> https:/
>
> Dear all,
>
> I need to install fenics into one of our servers running with opensuse 10
Which opensuse 10 version? There was a 10.2 and 10.3 version. Or did you
mean SUSE Linux 10 ?
>
> After some dependency problems, I am stuck with that problem:
>
> -------
> ...
> Processing enabled package: PyTrilinos
> -- Found PythonInterp: /usr/bin/python2.5 (Required is at least version "2.2")
> CMake Error at packages/
> Required NumPy python module not found
> Call Stack (most recent call first):
> packages/
>
>
> CMake Error at packages/
> SWIG was not found. Please specify Swig executable location
> Call Stack (most recent call first):
> packages/
>
>
> -- Configuring incomplete, errors occurred!
> -------
>
> Question: Should first the numpy installed (in standard repositories exists no package under the name numpy) ?
Since you are facing a rather old version of (open)suse and the build
service OBS does not support these ones
according to
http://
it will be difficult to find rpms (I guess). Have you tried to install
numpy directly, bypassing the package system? Last time I had to do that
it work flawlessly for me.
HTH
Andre
>
> You received this question notification because you are a member of
> DOLFIN Team, which is an answer contact for DOLFIN.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://
iQEcBAEBAgAGBQJ
uw4udJOdRmbbUUi
XnSGPmZGbG6iPZ3
ZDa6gsQ/
+zXWNSGTz+
PAk17k3gKUkS3EG
=ub4m
-----END PGP SIGNATURE-----
Revision history for this message
|
#2 |
sorry for the lack of info:
Linux version 2.6.25.
(gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) )
Revision history for this message
|
#3 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/07/2011 04:06 PM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> sorry for the lack of info:
>
> Linux version 2.6.25.
> (gcc version 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) )
>
Since rpm packages are difficult to get for that old suse variant I
would try to install the needed packages manually or with dorsal. Have
you already tried to use dorsal? If not, please have a look at it:
and its documentation describing how to use it to install FEniCS.
You could provide your own platform file including the packages you
need, for instance with the following content (depending on the packages
you want / or can principally install onyour system,
not completely sure about the PETSC_ARCH and SCOTCH_ARCH variables):
default PETSC_ARCH=
default SCOTCH_
# Define the packages this platform needs
PACKAGES=(
swig
numpy
parmetis
trilinos
petsc
slepc
armadillo
# swiginac
mtl
cgal
scientificpython
fiat
# ferari
ufc
ufl
ffc
# syfi
viper
instant
dolfin
)
Save this into a suse10.platform file and execute
./dorsal.sh suse10.platform
from with the dorsal folder.
No promise that it will work, but with some modification you might get
it to work (don't hesitate to ask!) There were a recent post in the
dorsal ml about successful installation on a rather ancient linux
(CentOS 5.5)
God luck,
Andre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://
iQEcBAEBAgAGBQJ
rUY1QLBDZnfqrgP
9T99g5v6QyiOj3L
dH2pcyu2hyj0h5l
OCADklnxvgN7MWa
iYdkNioR9LNzECS
=Rv/L
-----END PGP SIGNATURE-----
Revision history for this message
|
#4 |
Thanks a lot, I did a huge step, but PETSC exited somehow:
Install the project...
-- Install configuration: "RELEASE"
make: Leaving directory `/root/
Fetching petsc-3.1-p7
--2011-07-07 17:53:47-- http://
Resolving ftp.mcs.anl.gov... 140.221.6.23
Connecting to ftp.mcs.
HTTP request sent, awaiting response... 200 OK
Length: 15458474 (15M) [application/
Saving to: `petsc-
100%[==
2011-07-07 17:53:50 (5.59 MB/s) - `petsc-
Unpacking petsc-3.1-p7
Building petsc-3.1-p7
=======
=======
*******
-------
Nonexistent directory: /root/Work/
*******
after adding the directory:
Invalid library: /root/Work/
what is ?
with-ml
Revision history for this message
|
#5 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/07/2011 06:06 PM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> Thanks a lot, I did a huge step, but PETSC exited somehow:
>
>
> Install the project...
> -- Install configuration: "RELEASE"
> make: Leaving directory `/root/
> Fetching petsc-3.1-p7
> --2011-07-07 17:53:47-- http://
> Resolving ftp.mcs.anl.gov... 140.221.6.23
> Connecting to ftp.mcs.
> HTTP request sent, awaiting response... 200 OK
> Length: 15458474 (15M) [application/
> Saving to: `petsc-
>
> 100%[==
> 2.6s
>
> 2011-07-07 17:53:50 (5.59 MB/s) - `petsc-
> [15458474/15458474]
>
> Unpacking petsc-3.1-p7
> Building petsc-3.1-p7
> =======
> Configuring PETSc to compile on your system
> =======
> *******
> ERROR in COMMAND LINE ARGUMENT to config/configure.py
> -------
> Nonexistent directory: /root/Work/
> *******
>
>
> after adding the directory:
>
> Invalid library: /root/Work/
>
> what is ?
> with-ml
That means that petsc is configured to use the multilevel preconditioner
from the trilinos project, IIRC.
You have probably already check the the existence of the folder in
question? If not could you check the mentioned nonexistent directory and
the invalid library?
Did you see any suspicious output while compiling and installing
trilinos via dorsal?
In any case the complete dorsal terminal output might be interesting,
you can paste it e.g. at pastebin.com or at http://
(and your platform file in case you used a modified version of what I
suggested, the order of packages is important, and trilinos should come
before petsc)
Cheers,
- --
Andre
>
> You received this question notification because you are a member of
> DOLFIN Team, which is an answer contact for DOLFIN.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://
iQEcBAEBAgAGBQJ
/Mv6rYeqvwV+
uX3qRAkrwA6ZDwU
OtEZchV8R+
n+Mj7opoJZzES5J
i2eIxl30w7h9YlR
=L75E
-----END PGP SIGNATURE-----
Revision history for this message
|
#6 |
I added the directory manually than in a later step it could not find the library, the lib is really not there, platform is in the order as you proposed:
PACKAGES=(
swig
numpy
parmetis
trilinos
petsc
slepc
armadillo
# swiginac
mtl
scientificpython
fiat
# ferari
ufc
ufl
ffc
# syfi
viper
instant
dolfin
)
-------
the terminal output is http://
there are some NOT AVAILABLE warnings to the lapack-mtl and atlas packages, which is probably the failure of missing library, what do you think?
Revision history for this message
|
#7 |
On 07/08/2011 12:21 PM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> I added the directory manually than in a later step it could not find
> the library, the lib is really not there, platform is in the order as
> you proposed:
>
> PACKAGES=(
> swig
> numpy
> parmetis
> trilinos
> petsc
> slepc
> armadillo
> # swiginac
> mtl
> scientificpython
> fiat
> # ferari
> ufc
> ufl
> ffc
> # syfi
> viper
> instant
> dolfin
> )
>
> -------
> the terminal output is http://
>
> there are some NOT AVAILABLE warnings to the lapack-mtl and atlas
> packages, which is probably the failure of missing library, what do you
> think?
At a first quick look that is the reasons since Trilinos configuring end
up with the message:
WARNING: There were no packages configured so no libraries or
tests/examples will be built.
But that did not issue an error message, so dorsal kept running and
assumed ML to be in place. There are also some other libs missing, for
example the atlas lib...
However, to reduce the complexity of the compiling process and to
isolated error sources I would suggest that you start of with a
simplified version of the platform file to get a basic installation up
and running.
Swig, numpy, parmetis seem to be fine, but skip the trilinos package
(comment line with #) then petsc will not rely on that. To be absolutely
sure about that, wipe out the petsc folder (just leave the downloaded
tar.gz file there), since I have no clue about what petsc config scripts
might cache during the configure process.
Just to mentally prepare :) ourselves for some of the upcoming later
build failures (there will definitely a few more, I bet) : Is a recent
vtk and python-vtk version installed on your system (which one)?
Installing such a project as FEniCS with dependencies on other large
project on a older system which does not really feed us, is quite a bit
of a hassle, but I hope we get you through :)
HTH,
Andre
Revision history for this message
|
#8 |
thanks a lot for helping me through :)
first,l commenting trilinos helped but introduced another one: http://
second, if trilinos is commented, may I use the conjugated gradient iterative solver?
I run first, as commented in opensuse platform
# sudo zypper install -C lsb bzr subversion libxml2-devel gcc gcc-c++ \
# openmpi-devel python-devel python-numpy python-numpy-devel swig \
# wget boost-devel vtk-python liblapack3 libblas3 liblapack3 \
# mpfr-devel suitesparse-
# libumfpack5 CGAL-devel scotch-devel libatlas3-devel flex
so actually no ctk or python-vtk is installed, just get, thus:
... # rpm -qa | grep vtk
... # rpm -qa | grep python
python-
python-
python-2.5.2-26.6
python-
gimp-plugins-
python-
libvirt-
dbus-1-
python-
python-
python-
python-
python-
python-
libxml2-
python-
python-
python-
python-
python-
python-
python-
python-
python-
python-
Revision history for this message
|
#9 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Sorry for the late reply, but I have been without internet since Saturday.
On 07/08/2011 06:31 PM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> thanks a lot for helping me through :)
>
> first,l commenting trilinos helped but introduced another one: http://
Which one introduced you? It is a little hard to see from the output.
Did you change the suse11.platform file?
> second, if trilinos is commented, may I use the conjugated gradient iterative solver?
Yes, PETSC comes with one.
>
> I run first, as commented in opensuse platform
> # sudo zypper install -C lsb bzr subversion libxml2-devel gcc gcc-c++ \
> # openmpi-devel python-devel python-numpy python-numpy-devel swig \
> # wget boost-devel vtk-python liblapack3 libblas3 liblapack3 \
> # mpfr-devel suitesparse-
> # libumfpack5 CGAL-devel scotch-devel libatlas3-devel flex
These instruction are tailored for newer opensuse version and might not
apply in your case since
1. some of the instruction are outdated, e.g when it comes to swig and
newer dolfin version,
2. The instructions require adding some additional repos, which do
probably do not package the needed software for your suse version.
But could you specify exactly the suse version in question?
(Try a
cat /etc/issue
in a terminal)
That helps to narrow down which packages are available and which one you
have to compile yourself.
>
> so actually no ctk or python-vtk is installed, just get, thus:
>
> ... # rpm -qa | grep vtk
> ... # rpm -qa | grep python
> python-
> python-
> python-2.5.2-26.6
> python-
> gimp-plugins-
> python-
> libvirt-
> dbus-1-
> python-
> python-
> python-
> python-
> python-
> python-
> libxml2-
> python-
> python-
> python-
> python-
> python-
> python-
> python-
> python-
> python-
> python-
>
Then we have to add vtk as well, but first we should come as far as
possible with your current platform file.
Regarding your dorsal output: Have your checked whether parmetis
correctly installed, since the message
- --with-
did indicate that something went wrong.
Your should have a include/parmetis.h and a lib/libparmetis.a
file in the mentioned --with-parmetis-dir directory. And please check
the configure.log mentioned in the output to get an idea why petsc
failed. Your will find the log file in your petsc directory.
HTH
- --
Andre
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://
iQEcBAEBAgAGBQJ
qYl7tIgJbu/
ahkwrXMZGmxcamJ
bwESTJDmGgRFJFl
Gajvjc+
ro14fA5Iutyc3zO
=bOAW
-----END PGP SIGNATURE-----
Revision history for this message
|
#10 |
hi, thanks for the reply,
cat /etc/issue
Welcome to openSUSE 11.0 (X86-64) - Kernel \r (\l).
after commenting trilinos out in the suse11.3.platform it does not compile with errrors.
configure.log indicates that :
Possible ERROR while running linker: /root/Work/
initpart.
initpart.
initpart.
initpart.
initpart.
initpart.
initpart.
many times and gets out with:
File "./configure", line 257, in petsc_configure
framework.
File "/root/
child.
File "/root/
self.
File "/root/
ret = apply(test, args,kargs)
File "/root/
for location, directory, lib, incl in self.generateGu
File "/root/
raise RuntimeError(
by the way
/root/Work/FEniCS contains the files include/parmetis.h and lib/libparmetis.a
Revision history for this message
|
#11 |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07/13/2011 04:35 PM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> hi, thanks for the reply,
>
> cat /etc/issue
> Welcome to openSUSE 11.0 (X86-64) - Kernel \r (\l).
Ok. Then the
FEniCS/
file in your dorsal installation might be the best starting point (but
with the package list we used before) concerning the instructions, so
replace your platform file with that and comment out trilinos and add
swig as before.
The first thing is to check which of the mentioned additional repos also
exist for 11.0 (go to the sites and see whether a 11.0 is somewhere
lying around). Add existing ones via the zypper command.
Run the zypper install instruction and carefully follow which one are
missing.
>
> after commenting trilinos out in the suse11.3.platform it does not
> compile with errrors.
>
>
> configure.log indicates that :
> Possible ERROR while running linker: /root/Work/
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
Actually I have no idea what is going on here, but short googling + that
you mentioned an mpi problem in the beginning of the thread + that
libparmetis is mentioned already up-to-date makes me guessing that
something might be wrong/mixed with your mpi version(s). Please make
sure that your are using *openmpi* and wipe out the already installed
and build folders and completely rebuild them. When changing compilers,
libs version etc. your system could get messed up since your do not
compile/link consistently.
- --
Andre
>
> many times and gets out with:
>
> File "./configure", line 257, in petsc_configure
> framework.
> File "/root/
> child.configure()
> File "/root/
> self.executeTes
> File "/root/
> ret = apply(test, args,kargs)
> File "/root/
> for location, directory, lib, incl in self.generateGu
> File "/root/
> raise RuntimeError(
>
>
> by the way
> /root/Work/FEniCS contains the files include/parmetis.h and lib/libparmetis.a
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://
iQEcBAEBAgAGBQJ
XnuuMWy9w1inyL8
4wZui8559Lv42Pj
AKA6UZzucr0hcf4
4eZhOe8QUBC9le4
U0DF6gP8fjHgpMi
=PNbR
-----END PGP SIGNATURE-----
Revision history for this message
|
#12 |
It is not a good idea to install as root. Install it as a regular user.
More importantly, if you have root access you probably should upgrade the system to a more recent suse.
Harish
On Jul 13, 2011, at 4:35 PM, "B. Emek Abali" <email address hidden> wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> Status: Answered => Open
>
> B. Emek Abali is still having a problem:
> hi, thanks for the reply,
>
> cat /etc/issue
> Welcome to openSUSE 11.0 (X86-64) - Kernel \r (\l).
>
> after commenting trilinos out in the suse11.3.platform it does not
> compile with errrors.
>
>
> configure.log indicates that :
> Possible ERROR while running linker: /root/Work/
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
> initpart.
>
> many times and gets out with:
>
> File "./configure", line 257, in petsc_configure
> framework.
> File "/root/
> child.configure()
> File "/root/
> self.executeTes
> File "/root/
> ret = apply(test, args,kargs)
> File "/root/
> for location, directory, lib, incl in self.generateGu
> File "/root/
> raise RuntimeError(
>
>
> by the way
> /root/Work/FEniCS contains the files include/parmetis.h and lib/libparmetis.a
>
> --
> You received this question notification because you are a member of
> DOLFIN Team, which is an answer contact for DOLFIN.
Revision history for this message
|
#13 |
hi Harish, thanks for the suggestions, recent suse does not boot from xfs file system, which we cannot change, therefore the system will not be upgraded.
Is installing w/o root permissions the more appropriate way?
Revision history for this message
|
#14 |
On 7/14/11 10:55 AM, B. Emek Abali wrote:
> Question #164054 on DOLFIN changed:
> https:/
>
> B. Emek Abali posted a new comment:
> hi Harish, thanks for the suggestions, recent suse does not boot from
> xfs file system, which we cannot change, therefore the system will not
> be upgraded.
>
> Is installing w/o root permissions the more appropriate way?
>
In general, yes. This is only so that you (or dorsal) does not
accidentally mess anything up in the rest of the system.
Harish
Revision history for this message
|
#15 |
Thanks Andre Massing, that solved my question.