On Thursday September 16 2010 10:05:14 Anders Logg wrote:
On Thu, Sep 16, 2010 at 09:52:12AM -0700, Johan Hake wrote:
On Thursday September 16 2010 09:34:51 Johannes Ring wrote:
On Thu, Sep 16, 2010 at 5:22 PM, Johan Hake<johan.hake@xxxxxxxxx>
wrote:
On Thursday September 16 2010 04:37:49 Anders Logg wrote:
On Thu, Sep 16, 2010 at 11:16:29AM +0200, Johannes Ring wrote:
On Thu, Sep 16, 2010 at 9:28 AM, Anders Logg<logg@xxxxxxxxx>
wrote:
When I change something in DOLFIN and make a rebuild, I expect
to be able to enter the build directory and just type make
install, but frequently it starts a configure process which
fails and leaves me with a broken build directory and I need to
start from scratch with a clean build directory.
I have not had this problem.
What is the best way to make a rebuild?
I'm not sure, but what sort of changes do you make when this
happens
Change small things inside .cpp files.
I tried doing some changes but I couldn't reproduce your problem.
I might also have pulled some other changes.
and what error message do you get when the configure process
fails?
Many of these:
-- Configuring done
CMake Warning at dolfin/CMakeLists.txt:197 (add_library):
Cannot generate a safe runtime search path for target dolfin
because files
in some directories may conflict with libraries in implicit
directories:
runtime library [liblapack.so.3gf] in /usr/lib may be hidden
by
files in:
/usr/lib/atlas
runtime library [libblas.so.3gf] in /usr/lib may be hidden by
files in:
/usr/lib/atlas
Some of these libraries may not be found correctly.
I get this alot! I tried installing PETSc linking to installed blas
and lapack, but that turned out to just be too much hassle. Is this
a warning that we should take seriously? If not can we suppress it?
I also get a lot of those. One solution I found is to configure
DOLFIN with -DLAPACK_LIBRARIES=/usr/lib/liblapack.so.3gf. Another
is to remove the package libatlas-base-dev. None of these are good
solutions though.
I think we need to try to fix this as it is _really_ annoying. Can we
not suppres the warnings?
When did this show up? I suspect Garth added this. :-)
I think he added the demos to the configuration and these just repeated
the same error. The error were there before the demos was added.
The warning is a valid warning a guess. It tells us that we have two
libraries with the same name in the path. The problem is that we know
this and we think it is fine, so we would rather not get the message.
