 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When I try to build the boost library, I get complaints about MPI, bzip2, and
python. Specifically:
______________________________________________________________________
warning: Graph library does not contain MPI-based parallel components.
note: to enable them, add "using mpi ;" to your user-config.jam
- iconv (libc) : yes
- icu : no
- icu (lib64) : no
- ../config//has_gcc_visibility builds : yes
- ../config//has_long_double_support builds : yes
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.
______________________________________________________________________
Plus 2 bzip2-related modules and 56 python-related modules that won't compile.
I'll keep trying to figure this stuff out (note: unless someone posts that I can
safely ignore these messages). But first, I'm gonna watch the New England
Patriots beat the Baltimore Ravens.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/22/2012 04:11 PM, Cousin Ricky wrote:
> When I try to build the boost library, I get complaints about MPI, bzip2, and
> python. Specifically:
> ______________________________________________________________________
>
> warning: Graph library does not contain MPI-based parallel components.
> note: to enable them, add "using mpi ;" to your user-config.jam
> - iconv (libc) : yes
> - icu : no
> - icu (lib64) : no
> - ../config//has_gcc_visibility builds : yes
> - ../config//has_long_double_support builds : yes
> warning: skipping optional Message Passing Interface (MPI) library.
> note: to enable MPI support, add "using mpi ;" to user-config.jam.
> note: to suppress this message, pass "--without-mpi" to bjam.
> note: otherwise, you can safely ignore this message.
> ______________________________________________________________________
>
> Plus 2 bzip2-related modules and 56 python-related modules that won't compile.
>
> I'll keep trying to figure this stuff out (note: unless someone posts that I can
> safely ignore these messages). But first, I'm gonna watch the New England
> Patriots beat the Baltimore Ravens.
well ... being as it says optional my 1st guess be that my /might/
squeak by but if it were me I'd want to resolve to before forging ahead.
As for the Pats beating the Ravens ... being as it was 13 - 10 at the
half I don't think it's going to be the cakewalk that some predicted ...
Brady seems off. The better game will be the night-cap ... Go 9ers!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
<offtopic>
Jim Holsenback <nom### [at] nomail com> wrote:
> As for the Pats beating the Ravens ... being as it was 13 - 10 at the
> half I don't think it's going to be the cakewalk that some predicted ...
> Brady seems off. The better game will be the night-cap ... Go 9ers!
Yeah, Brady's definitely off tonight. :-(
</offtopic>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 22/01/2012 22:11, Cousin Ricky nous fit lire :
> When I try to build the boost library, I get complaints about MPI, bzip2, and
> python. Specifically:
> ______________________________________________________________________
>
> warning: Graph library does not contain MPI-based parallel components.
> note: to enable them, add "using mpi ;" to your user-config.jam
> - iconv (libc) : yes
> - icu : no
> - icu (lib64) : no
> - ../config//has_gcc_visibility builds : yes
> - ../config//has_long_double_support builds : yes
> warning: skipping optional Message Passing Interface (MPI) library.
> note: to enable MPI support, add "using mpi ;" to user-config.jam.
> note: to suppress this message, pass "--without-mpi" to bjam.
> note: otherwise, you can safely ignore this message.
> ______________________________________________________________________
>
> Plus 2 bzip2-related modules and 56 python-related modules that won't compile.
>
> I'll keep trying to figure this stuff out (note: unless someone posts that I can
> safely ignore these messages). But first, I'm gonna watch the New England
> Patriots beat the Baltimore Ravens.
>
>
>
Boost & Python ??? uh !
I thought Boost was about C++.
AFAIK, you do not need the graph library of boost for povray.
needed are hash, thread, weak_ptr, scoped_ptr, unordered_map, condition,
string algorithm, date & time, math fancies (common factor as well as
mersenne twister... and more)... but no graph.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/22/2012 05:30 PM, Le_Forgeron wrote:
> needed are hash, thread, weak_ptr, scoped_ptr, unordered_map, condition,
> string algorithm, date& time, math fancies (common factor as well as
> mersenne twister... and more)... but no graph.
hmmm ... I only managed to recall 4 from your list. What about the "and
more"? Would the work that's being done for the windows source build,
that was recently checked in be helpful in completing this list? I think
this comes under the heading of good to know information, and I'd be
willing to do the busy work
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 23/01/2012 00:09, Jim Holsenback nous fit lire :
> On 01/22/2012 05:30 PM, Le_Forgeron wrote:
>> needed are hash, thread, weak_ptr, scoped_ptr, unordered_map, condition,
>> string algorithm, date& time, math fancies (common factor as well as
>> mersenne twister... and more)... but no graph.
>
> hmmm ... I only managed to recall 4 from your list. What about the "and
> more"? Would the work that's being done for the windows source build,
> that was recently checked in be helpful in completing this list? I think
> this comes under the heading of good to know information, and I'd be
> willing to do the busy work
I just did a quick (and very dirty) :
grep -r boost . |grep include |sed -e "s/^.*://g" |sort |sort -u
(and it has still many rubbishes) on the sources... I'm not sure to
identify all the primary components of boost (vs the subtilities of
smaller components; I'm not that familiar with their packaging)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I added "using mpi ;" to my user-config.jam. I got back:
________________________________________________________________________
MPI auto-detection failed: unknown wrapper compiler mpic++
Please report this error to the Boost mailing list: http://www.boost.org
You will need to manually configure MPI support.
________________________________________________________________________
I don't like getting messages like this. >:-(
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 23/01/2012 02:28, Cousin Ricky a écrit :
> I added "using mpi ;" to my user-config.jam. I got back:
> ________________________________________________________________________
>
> MPI auto-detection failed: unknown wrapper compiler mpic++
> Please report this error to the Boost mailing list: http://www.boost.org
> You will need to manually configure MPI support.
> ________________________________________________________________________
>
> I don't like getting messages like this. >:-(
AFAIK, you do not need MPI (optimisation of code by compiler applied to
sequential code to use parallelism when available and triggered by the
code itself). The parallelism of povray 3.7 is explicit, using threads.
Otherwise, you should install "Open MPI" to get with the installation of
mpic++ (which is a wrapper on your usual c++ compiler, so if your g++ is
out of date, that will be yet another story)
http://www.open-mpi.org/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le_Forgeron <lef### [at] freefr> wrote:
> Le 23/01/2012 02:28, Cousin Ricky a écrit :
> > I added "using mpi ;" to my user-config.jam. I got back:
> > ________________________________________________________________________
> >
> > MPI auto-detection failed: unknown wrapper compiler mpic++
> > Please report this error to the Boost mailing list: http://www.boost.org
> > You will need to manually configure MPI support.
> > ________________________________________________________________________
> >
> > I don't like getting messages like this. >:-(
>
> AFAIK, you do not need MPI (optimisation of code by compiler applied to
> sequential code to use parallelism when available and triggered by the
> code itself). The parallelism of povray 3.7 is explicit, using threads.
I went ahead with the POV installation and got back:
__________________________________________________________________
[snip]
checking for g++ version... 4.6
checking for ranlib... ranlib
Libraries
---------
checking whether to link with cygwin DLL... no
checking whether to enable static linking... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for boostlib >= 1.37... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the boost thread library is usable... no
configure: error: in `/home/ricky/povray/povray-3.7.0.RC3':
configure: error: cannot link with the boost thread library
See `config.log' for more details.
__________________________________________________________________
No complaints about MPI, Bzip2, or Python in the config.log file. Whatever the
problem is, it appears to be in the Boost installation, or lack thereof.
> Otherwise, you should install "Open MPI" to get with the installation of
> mpic++ (which is a wrapper on your usual c++ compiler, so if your g++ is
> out of date, that will be yet another story)
>
> http://www.open-mpi.org/
Tried that, got the same message from Boost installation.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Additional information from config.log:
_____________________________________________________________________________
configure:7645: checking whether the boost thread library is usable
configure:7665: g++ -o conftest -pthread -pthread -I/usr/local/include
-L/usr/local/lib conftest.cpp -lboost_thread -pthread >&5
configure:7665: $? = 0
configure:7665: ./conftest
../conftest: error while loading shared libraries: libboost_thread.so.1.48.0:
cannot open shared object file: No such file or directory
configure:7665: $? = 127
configure: program exited with status 127
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "POV-Ray"
| #define PACKAGE_TARNAME "povray"
| #define PACKAGE_VERSION "3.7.0.RC3"
| #define PACKAGE_STRING "POV-Ray 3.7.0.RC3"
| #define PACKAGE_BUGREPORT "REDACTED"
| #define PACKAGE_URL ""
| #define VERSION_BASE "3.7"
| #define DISTRIBUTION_MESSAGE_2 " Richard Callwood III <REDACTED>"
| #define PACKAGE "povray"
| #define VERSION "3.7.0.RC3"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_STDLIB_H 1
| #define BUILD_ARCH "i686-pc-linux-gnu"
| #define COMPILER_VENDOR "gnu"
| #define COMPILER_VERSION "g++ 4.6"
| #define COMPILER_VER " (g++ 4.6 @ i686-pc-linux-gnu)"
| #define HAVE_PTHREAD 1
| #define HAVE_BOOST /**/
| #define HAVE_BOOST_THREAD /**/
| /* end confdefs.h. */
|
| #include <boost/thread/thread.hpp>
|
| int
| main ()
| {
| boost::defer_lock_t(); return 0;
| ;
| return 0;
| }
configure:7670: result: no
configure:7672: error: in `/home/ricky/povray/povray-3.7.0.RC3':
configure:7675: error: cannot link with the boost thread library
See `config.log' for more details.
_____________________________________________________________________________
From the bash terminal session:
________________________________________________________________________________
linux-g9n0:/usr/local/boost_1_48_0 # find /usr -name 'libboost_thread*' -print
/usr/local/boost_1_48_0/stage/lib/libboost_thread.a
/usr/local/boost_1_48_0/stage/lib/libboost_thread.so
/usr/local/boost_1_48_0/stage/lib/libboost_thread.so.1.48.0
/usr/local/boost_1_48_0/bin.v2/libs/thread/build/gcc-4.6/release/link-static/threading-multi/libboost_thread.a
/usr/local/boost_1_48_0/bin.v2/libs/thread/build/gcc-4.6/release/threading-multi/libboost_thread.so.1.48.0
/usr/local/lib/libboost_thread.a
/usr/local/lib/libboost_thread.so
/usr/local/lib/libboost_thread.so.1.48.0
/usr/lib/libboost_thread.so.1.46.1
________________________________________________________________________________
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
