dolfin team mailing list archive

["Martin Sandve Alnæs" <martinal@xxxxxxxxx>]

2008/4/22, Anders Logg <logg@xxxxxxxxx>:
> On Tue, Apr 22, 2008 at 10:59:29AM -0400, Hatef Monajemi wrote:
>  >
>  >
>  >
>  > Anders Logg wrote:
>  >
>  >
>  > >On Tue, Apr 22, 2008 at 11:26:06AM +0100, Garth N. Wells wrote:
>  > >>
>  > >>
>  > >> Anders Logg wrote:
>  > >> > On Tue, Apr 22, 2008 at 10:54:29AM +0200, Martin Sandve Alnæs wrote:
>  > >> >> 2008/4/22, Ilmar Wilbers <ilmarw@xxxxxxxxx>:
>  > >> >>>  Garth N. Wells wrote:
>  > >> >>>  >
>  > >> >>>  >
>  > >> >>>  > Ilmar Wilbers wrote:
>  > >> >>>  >> Anders Logg wrote:
>  > >> >>>  >>> On Mon, Apr 21, 2008 at 10:14:51PM -0400, Hatef Monajemi
>  > wrote:
>  > >> >>>  >>>
>  > >> >>>  >>>> Hello
>  > >> >>>  >>>> I am trying to install FEniCS on some new machines. I follow
>  > the
>  > >> >>>  >>>> instructions mentioned in the Fenics document for
>  > installation,
>  > >> >>>  >>>> However when I try to run a demo, there is an error in
>  > "make" step.
>  > >> >>>  >>>> the error is as follows:
>  > >> >>>  >>>>
>  > >> >>>  >>>>
>  > ---------------------------------------------------------------
>  > >> >>>  >>>> rm -f *.o core *.core main.o demo
>  > >> >>>  >>>> `pkg-config --variable=compiler dolfin` `pkg-config --cflags
>  > >> >>>  >>>> dolfin` -c main.cpp
>  > >> >>>  >>>> `pkg-config --variable=compiler dolfin` -o demo main.o
>  > `pkg-config
>  > >> >>>  >>>> --cflags dolfin` `pkg-config --libs dolfin`
>  > >> >>>  >>>> /usr/bin/ld: cannot find -lamd
>  > >> >>>  >>>> collect2: ld returned 1 exit status
>  > >> >>>  >>>> make: *** [demo] Error 1
>  > >> >>>  >>>>
>  > ----------------------------------------------------------------
>  > >> >>>  >>>>
>  > >> >>>  >>>> does anyone know how I can get rid of this -lamd error???
>  > >> >>>  >>>>
>  > >> >>>  >>> Do you have libamd on the system? Try with
>  > >> >>>  >>>
>  > >> >>>  >>> locate libamd
>  > >> >>>  >>>
>  > >> >>>  >>>
>  > >> >>>  >> libamd should be installed as part of umfpack. For Ubuntu,
>  > libamd.so
>  > >> >>>  >> comes with libsuitesparse-dev and libufsparse-dev.
>  > >> >>>  >
>  > >> >>>  > Is limamd not tested for by umfpack.py?
>  > >> >>>  >
>  > >> >>>
>  > >> >>> Yes, it is. Both the location of the header files and of the
>  > library
>  > >> >>>  files are located. I get an error using scons when the
>  > dev-packages are
>  > >> >>>  not installed.
>  > >> >>>
>  > >> >>>  Maybe Hatef could run 'python umfpack.py' in
>  > >> >>>  dolfin/scons/simula-scons/simula_scons/pkgconfiggenerators, and
>  > include
>  > >> >>>  the output (if any error), as well as the file umfpack.pc that
>  > will be
>  > >> >>>  generated in the same folder.
>  > >> >>>
>  > >> >>>  Also, the file dolfin/scons/simula_scons.log could be of
>  > interest. It is
>  > >> >>>  generated when using scons in the main dolfin folder.
>  > >> >>>
>  > >> >>>
>  > >> >>>  ilmar
>  > >> >> He said he's using make, not the new scons build system.
>  > >> >
>  > >> > ok, then the answer is "Use the new build system".
>  > >> >
>  > >>
>  > >> Or "Let's make a release".
>  > >>
>  > >> Garth
>  > >
>  > >:-)
>  > >
>  > >I'm working on a cleanup/review of the linear algebra classes.
>  > >Hopefully I can finish today and then I'm ready for a release.
>  > >
>  >
>
> > Thank you for your replies.
>  > Yes, as you mentioned, I am using the old build system not the new
>  > Scons one.
>  > now, is there any document or example which shows how to use Scons as a
>  > build system for Fenics. Because I installed Fenics based on what has
>  > been mentioned in Download page of www.fenics.org using apt-get and
>  > also installed all the dependencies mentioned in Dolfin user manual but
>  > I could not find anything related to Scons in documentation.
>  >
>  > I hope as Anders said this new release will solve the problem.
>  >
>  > Hatef
>
>
> See here:
>
>   http://www.fenics.org/wiki/Compiling_DOLFIN
>
>  --
>
> Anders


This has been fixed:

    * The scons-based build process will create some pkg-config files,
and try to write these files in the first writable directory in your
PKG_CONFIG_PATH environment. We strongly suggest that you create a
specific directory for this use by, e.g.,


--
Martin