No I didn't because I don't have the rights on the machine to execute sudo
apt-get ...

What surprises me is that I hadn't had that problem before the ubuntu
update.
In any case, I downloaded the most recent Boost version and set both
BOOST_LIBRARYDIR
and BOOST_ROOT to the new location of Boost but it gives almost the same
error:

CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:1131 (message):

  Unable to find the requested Boost libraries.


  Boost version: 1.56.0


  Boost include path: /home/vyl/boost_1_56_0


  Could not find the following Boost libraries:


          boost_filesystem

          boost_program_options

          boost_system

          boost_thread

          boost_iostreams


  No Boost libraries were found.  You may need to set BOOST_LIBRARYDIR to
the

  directory containing Boost libraries or BOOST_ROOT to the location of

  Boost.


 except that /home/vyl/boost_1_56_0 should be the right folder...


Thanks for your time!

Vincent


On Thu, Aug 14, 2014 at 2:05 AM, Johannes Ring <[email protected]> wrote:

> On Wed, Aug 13, 2014 at 5:15 PM, Laboure, Vincent M
> <[email protected]> wrote:
> > ...
> > CMake Error at /usr/share/cmake-2.8/Modules/FindBoost.cmake:1131
> (message):
> >   Unable to find the requested Boost libraries.
> >
> >   Boost version: 1.54.0
> >
> >   Boost include path: /usr/include
> >
> >   Could not find the following Boost libraries:
> >
> >           boost_filesystem
> >           boost_program_options
> >           boost_system
> >           boost_thread
> >           boost_iostreams
> >
> >   No Boost libraries were found.  You may need to set BOOST_LIBRARYDIR
> to the
> >   directory containing Boost libraries or BOOST_ROOT to the location of
> >   Boost.
> > ...
>
> The Boost libraries are missing. Did you follow the instructions to
> install the packages via apt-get when you ran Dorsal?
>
> Johannes
>
_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to