|
From: | Eugenio Gianniti |
Subject: | [fem-fenics] Build system |
Date: | Thu, 6 Mar 2014 16:09:05 +0000 |
I attach the preliminary patch (pkg-config-patch.diff) I’m using so that you know what are my edits.
I was able to install both the Forge package and the one I’m testing. I noticed going through the Forge distributed tarball that I needed to ./bootstrap my version before packaging.
I wasn’t able to have a successful run of the examples with neither of the two, so I attach a comprehensive set of errors and crashes (errors.txt) to ask for advice. Here I summarise my attempts for your convenience:
1) Installing the Forge fem-fenics with the suggested export of the preprocessor flags leads in most cases to an Octave crash for a failed symbol lookup related to an openmpi shared library
2) Installing my tarball with the suggested environment ends up as (1)
3) If after installing the Forge package as in (1) I unset CPPFLAGS Octave errors out with a compilation error due to the <Eigen/Dense> missing include
4) Without CPPFLAGS set my tarball does install, anyway Octave errors out as in (3)
5) It is not reported in the attachment, but the Forge package doesn’t install without exporting CPPFLAGS
First of all I’d like to know if the openmpi issue is known and, in case, I would kindly ask for a reference to where it is addressed. Furthermore, examples (3) and (4) suggest that the build system is fragile to headers which are not in the standard include
directories. I would propose to add proper environment variables definitions through PKG_ADD [1]. If I’m not getting it wrong that file allows for Octave commands to be run at the moment of loading the package. I would use a system() call like others I can
see in the core repository m-files. Anyway I don’t know if such a call supports setting environment variables: the best situation would be if they were set for the Octave process and then unset after exiting. Actually I expect this latter behaviour, since
./octave is executed and not sourced, but I would like to know if exporting in the first place is possible.
Eugenio
|
pkg-config-patch.diff
Description: pkg-config-patch.diff
errors.txt
Description: errors.txt
|
[Prev in Thread] | Current Thread | [Next in Thread] |