[MOAB-dev] problem with pcomm

[Vijay S. Mahadevan]

Thanks for checking this Lorenzo. I'll see if I can replicate the
dual_test issue locally.

Also, line 637 should probably not be changed since it tackles
Clang+Linux combinations. I'll submit a PR with these changes after my
local tests pass. Do you have a bitbucket account so that I can add
you as a reviewer ?

Vijay

On Thu, Dec 3, 2015 at 10:45 AM, Lorenzo Alessio Botti
<bottilorenzo at gmail.com> wrote:
> 636   Clang:*)
>
> 637     FATHOM_CXX_SPECIAL="$EXTRA_GNU_FLAGS -stdlib=libc++"
>
> 638     FATHOM_CXX_32BIT=-m32
>
> 639     FATHOM_CXX_64BIT=-m64
>
> 640     ;;
>
> 641   SunWorkshop:i?86|SunWorkshop:x86_64)
>
> 642     FATHOM_CXX_32BIT=-m32
>
> 643     FATHOM_CXX_64BIT=-m64
>
> 644     ;;
>
> 645   *)
>
> 646     ;;
>
> 647 esac
>
> 648 AC_MSG_RESULT([$cxx_compiler:$host_os:$host_cpu])
>
> 649
>
> 650 # Check for specific overrides
>
> 651 CXX_LDFLAGS=""
>
> 652 if (test "$cxx_compiler:${host_os:0:6}" == "Clang:darwin"); then
>
> 653   CXX_LDFLAGS="$CXX_LDFLAGS -stdlib=libc++"
>
> 654   LIBS="$LIBS -lc++”
>
>
> I changed lines 637 and 653 of compilers.m4 as you suggested (libc++ instead
> of libstdc++).
> My code runs fine (I’m on Mavericks with latests clang).
> As opposite to the previous build make check now get suck at dual_test.
> The other tests runs fine.
>
> Thanks everybody for help!
> As Vijay pointed out I thinks this is the way to go since it allows to use
> c++11.
>
> Thanks again.
> Bests.
> Lorenzo
>
>