Unable to build vim-gtk2 using clang; hack in system includes

[Jan Danielsson <jan.m.danielsson%gmail.com@localhost>]

Hello,

   I'm getting the following error:

[---]
clang++ -I/usr/include -D_REENTRANT  -DU_HAVE_ELF_H=1
-DU_HAVE_NETBSD_ATOMIC_OPS=1 -DU_HAVE_STD_STRING=0 -DU_HAVE_ATOMIC=0
-I.   "-DDEFAULT_ICU_PLUGINS=\"/usr/pkg/lib/icu\" "
-DU_ATTRIBUTE_DEPRECATED= -DU_COMMON_IMPLEMENTATION  -O2 -pipe
-I/usr/include -W -Wall -pedantic -Wpointer-arith -Wwrite-strings
-Wno-long-long --std=c++0x  -Qunused-arguments -Wno-parentheses-equality
 -c   -o uvectr32.ao uvectr32.cpp
In file included from ustrenum.cpp:1:
In file included from ustrenum.cpp:11:
In file included from ./utypeinfo.h:29:
In file included from /usr/include/g++/typeinfo:35:
In file included from /usr/include/g++/exception:151:
/usr/include/g++/nested_exception.h:122:61: error: redefinition of
default argument
    __throw_with_nested(_Ex&& __ex, const nested_exception* = 0)
                                                            ^ ~
/usr/include/g++/nested_exception.h:110:56: note: previous definition is
here
    __throw_with_nested(_Ex&&, const nested_exception* = 0)
                                                       ^ ~
1 error generated.
../config/mh-bsd-gcc:41: recipe for target 'ustrenum.ao' failed
[---]

   Inspecting nested_exception.h:

[---]
  template<typename _Ex>
    void
    __throw_with_nested(_Ex&&, const nested_exception* = 0)
    __attribute__ ((__noreturn__));
[---]
  // This function should never be called, but is needed to avoid a warning
  // about ambiguous base classes when instantiating
throw_with_nested<_Ex>()
  // with a type that has an accessible nested_exception base.
  template<typename _Ex>
    inline void
    __throw_with_nested(_Ex&& __ex, const nested_exception* = 0)
    { throw __ex; }
[---]

   Need hack to avoid problem.  Hack breaks build.  C++ makes me sad.  :(

   I've had default argument errors when building "gcc" C++ code with
clang before, but fixing those problems have been very straight forward.
 In this case I'm not sure what the appropriate solution is.

-- 
Kind Regards,
Jan