Hanspeter,
Just to clarify things, the history of openmpi is as follows.
Originally when I picked up the package it was designed to use only
the fortran compiler from the gcc4x-compiler packages and the system gcc
and cc compilers were used for c and c++ code. I got
a number of user
Hanspeter,
I would also point out that the reason that the boost1.xx releases
prior to boost1.53 don't exist on 10.9 is that
boost1.53 was the first release sufficiently patched for libc++ to properly
build against the new default c++ library
on 10.9. If you had problems building boost1.55
Hanspeter,
Okay, I see now that you are trying to leverage the openmpi support in
boost. This creates two different problems.
1) On 10.8 and earlier, openmpi uses the gcc-fsf-4.8 and g++-fsf-4.8
compilers so you would need to compile boost against that compiler.
However this will mean that
Hanspeter,
What is the logic behind making boost1.55 build against the
g++-fsf-4.8 compiler instead of clang++ on 10.9 and later? By doing that,
you require any program that links against boost1.55 and all of its support
libraries to be built with g++-fsf-4.8. We were very careful when
Hanspeter,
I committed the following changes to boost1.55.info in 10.7 tree
which rationalizes the packaging on 10.9 so that it
builds against the correct libc++ c++ library (which is the same one that
openmpi on 10.9 or later uses)…
Index: boost1.55.info
Hanspeter,
It appears that the boost.mpi support can be tested (according to
http://www.boost.org/doc/libs/1_55_0/doc/html/mpi/getting_started.html)
as follows. On a build with 'fink -m -kK', execute…
cd /sw/src/fink.build/boost1.55-nopython-1.55.0-2/boost_1_55_0/libs/mpi/test
On Sat, April 26, 2014 11:14 am, Jack Howarth wrote:
Hanspeter,
What is the logic behind making boost1.55 build against the
g++-fsf-4.8 compiler instead of clang++ on 10.9 and later? By doing that,
you require any program that links against boost1.55 and all of its
support
libraries to
Hanspeter,
No problem. On 10.8 and earlier, there isn't a completely painless
option. Mixing the two different libstdc++'s
by linkage into the same program can be a tricky proposition, but reverting
openmpi to build against the system libstdc++
will also break existing binaries. However,
