install dolfin

Hello!

In what directory are you in? Have you created a build director which you have
entered? Then you need to change the configuration call to:

  cmake .. -DCMAKE_INSTALL_PREFIX=~/local

Johan

On Tuesday August 31 2010 20:04:04 chunhe lee wrote:
> New question #123579 on DOLFIN:
> https://answers.launchpad.net/dolfin/+question/123579
>
> I followed the steps of Manual installation from source. when I run "cmake
> . -DCMAKE_INSTALL_PREFIX=~/local" to install dolfin, it saids no
> CMakeLists.txt. Do I need to write CMakeLists.txt by myself? or it does
> not work using cmake to install dolfin?. Thanks!

What version of DOLFIN are you using? The previous release wasn't based on CMake, but used SCons instead. Maybe this is the issue you have run into.

Thanks, what I used is the latest DOLFIN 0.9.8, It has something about Scons in the package like you said. But if this version does not support Cmake, which version does?

Harish Narayanan said 1 hour ago:
What version of DOLFIN are you using? The previous release wasn't based on CMake, but used SCons instead. Maybe this is the issue you have run into.

Thanks, the directory is dolfin-0.9.8, it include a scons folder, and a script scons.local, I don't know if I should firstly install scon.

Johan Hake said 1 hour ago:
Hello!

In what directory are you in? Have you created a build director which you have
entered? Then you need to change the configuration call to:

  cmake .. -DCMAKE_INSTALL_PREFIX=~/local

Johan

On Wed, Sep 01, 2010 at 05:55:16AM -0000, chunhe lee wrote:
> Question #123579 on DOLFIN changed:
> https://answers.launchpad.net/dolfin/+question/123579
>
> Status: Answered => Open
>
> chunhe lee is still having a problem:
> Thanks, what I used is the latest DOLFIN 0.9.8, It has something about
> Scons in the package like you said. But if this version does not support
> Cmake, which version does?

No version yet, but we are working on it. Perhaps there will be a
0.9.9 release in the very near future.

--
Anders

Thank you, but if cmake does not work, could you tell me how to install dolfin, should I firstly install scons?

Yes, you should first install SCons. Ignore the CMake-related instructions, as they are not applicable to the version you are working with, and follow the file INSTALL in the DOLFIN source that you downloaded.

Thanks Harish Narayanan, that solved my question.

I have installed scons, but when I tried to run scons to install ufc-1.4.1, it appears:

scons: Reading SConscript files ...
  File "/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.1/SConstruct", line 99

    end_message += """
---------------------------------------------------------
*** Warning: Old ufc module

%s

still excists in installation path.
Try remove these files with:

    scons -c cleanOldUFC=Yes

Note that you may need to be root.
"""%("\n".join(" " + m for m in old_ufc_modules))

When I run "scons -c cleanOldUFC=Yes", it still appear these sentence, how should I continue? thanks!

You can delete the files by hand - remove ufc.h in <prefix>/include and any ufc files in

    <prefix>/lib/python2.x/dist-packages

or

   <prefix>/lib/python2.x/site-packages

Thanks to Garth Wells, I find ufc.h and ufc*.* in my directory, but no related files. Also I checked the directory <prefix>/lib/python2.x/site-packages, there are not ufc files. Do I need to be root to find other directories? Now I don't have the root right.

On Thu, Sep 02, 2010 at 01:45:08AM -0000, Chunhe Lee wrote:
> Question #123579 on DOLFIN changed:
> https://answers.launchpad.net/dolfin/+question/123579
>
> Status: Answered => Open
>
> Chunhe Lee is still having a problem:
> Thanks to Garth Wells, I find ufc.h and ufc*.* in my directory, but no
> related files. Also I checked the directory <prefix>/lib/python2.x
> /site-packages, there are not ufc files. Do I need to be root to find
> other directories? Now I don't have the root right.

I suggest you try the latest stable release instead. I just came out a
couple of hours ago.

Take a look at the installation instructions here:

  http://www.fenics.org/doc

--
Anders

Thanks, I have tried the latest ufc-1.4.2. I followed the instruction of README,
When I run: cmake -D -DCMAKE_INSTALL_PREFIX=~/bin/ufc, it's ok, but when I run "make install", there are errors. What does this mean?

/opt/cluster/cmake/bin/cmake -H/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2 -B/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2 --check-build-system CMakeFiles/Makefile.cmake 0
/opt/cluster/cmake/bin/cmake -E cmake_progress_start /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/CMakeFiles /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[1]: Entering directory `/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2'
make -f CMakeFiles/_ufc.dir/build.make CMakeFiles/_ufc.dir/depend
make[2]: Entering directory `/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2'
/opt/cluster/cmake/bin/cmake -E cmake_progress_report /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/CMakeFiles 2
[ 50%] Swig source
/usr/bin/swig -python -module ufc -outdir /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2 -c++ -I/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/src/ufc -I/usr/include -I/usr/include/python2.3 -o /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/src/ufc/ufcPYTHON_wrap.cxx /RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/src/ufc/ufc.i
/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2/src/ufc/ufc.i:14: Unable to find 'boost_shared_ptr.i'
make[2]: *** [src/ufc/ufcPYTHON_wrap.cxx] Error 1
make[2]: Leaving directory `/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2'
make[1]: *** [CMakeFiles/_ufc.dir/all] Error 2
make[1]: Leaving directory `/RAID/rhome/lihe/program/temp/FEniCS/ufc-1.4.2'
make: *** [all] Error 2

Perhaps you could try to use the FEniCS install script, Dorsal, rather than attempting to build it by hand.

(But in order for it to be convenient, you need root access on the machine you are working with. And I don't think you have it given the paths on your error logs.)

And in the future, when a question is marked as solved, please don't reopen it unless you have the same question again. Since this is a different question you are now asking, you should open a new one.